Reading the pulse of an offshore Project - what to look for?

Have you been thorough the process of outsourcing your Agile project to an offshore service provider? If yes - you must have wondered how you should be measuring the progress & success of the work that is getting carried out by your service provider. But what could be the measuring criteria? How do you know if you are heading the right direction or not?

In this session we look in to the aspects of identifying how one may successfully measure the state of an ongoing delivery model & based on it, how we refine/improve the outcome.

Backdrop:

Over the last 10 years while working in onsite-offshore model, what I have personally come across is the fact - whenever we work on Agile, we do come across one magic phrase every now & then - "I have also worked on Agile". Yes, we all have! :) Agile is simple & there is no rocket science in doing so while delivering across onsite & offshore. We all know the drill i.e. set up some time zone overlaps, establish virtual communication channels, identify some Proxy POs, have some kind of "all hands" infrequently & we should be good. Isn't it?

We all know these (at least we all claim so)! But then why is it that some of the projects do better than the rest & some even fail? Why is this that we don't realize that if you offshore your work in Kolkata, you deal with a different cultural barrier than if you offshore the work at Bangalore (or vice versa)? Did we ever consider that it is upon us - the so called Agilists - to bring up the Agile knowhow to our clients (& many a times - learn from clients as well)? These are the simple - yet mostly unnoticed elements - which play a crucial role in deciding how a project succeeds in Agile offshoring & we should be able to take them in to consideration.

 
1 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The discussion has been kept to 20 minutes. Intentionally a small window - as the intent is to spark the thought process & encourage all to think on these lines. 

  1. Offshoring is done with specific objectives in mind - what are the general ones?
  2. How do we measure weather those objectives are met or not?
  3. But beyond the financials (time & budget), how do we measure the success of "Business Value Delivery" (BVD)?
  4. What are the key KPIs one should look for to understand how far BDV is made?
  5. How do we measure the KPIs & how do we get genuine data (e.g. in a Sprint, a team will generally meet it's committment - as it may start with a low figure, and gradually will pull in as it progresses & eventually end up victorious)?
  6. Good, bad & the ugly truth about Agile Offshoring

 

Learning Outcome

This session focuses on providing a guidance towards how offshore projects typically tend to drive the work & what could be the areas - always under radar from client perspective. It provides opportunity to both client & service providers to improve the ongoing process.

 

Specific focus on the followings:

  1. What to look for - when you try to measure your progress?
  2. How do you look for the right answers?
  3. When you get the answers, how do you derive your report?
  4. Corrections? What & how?

 

Target Audience

Agile Managers, Coaches, CEO, CIO, CFO, Vendor Managers, Project Managers, Program Managers, Scrum Masters

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ravi Kumar
    By Ravi Kumar  ~  3 years ago
    reply Reply

    Hi Arijit,

     

    The slides shared don't corelate to your proposal. Can you post a link to a video on this topic that you have proposed and also any write-ups/article describing the key outcomes.

     

    Best,

     

    Ravi

  • Pavel Dabrytski
    By Pavel Dabrytski  ~  3 years ago
    reply Reply

    Hi Arijit,

    Thank you for your submission!

    Can you give us some examples of the metrics (ways you propose to measure the progress). We would like to understand if this is something our audience will be interested in.

    Also I am concerned (you are welcome to ingnore it) that it might be too much material to cover in 20 minutes. ;-) Perhaps to focus on 2-3 main ideas instead.

    if you find my questions/suggestions above useful, please don't put your reply in the comment, rather update the proposal, it will increase you chances to get accepted.

    Regards. Pavel.

     

     

     

  • Raja Bavani
    By Raja Bavani  ~  3 years ago
    reply Reply

    Dear Arjit,

    Let us look at  onsite or collocated agile projects, and offshore projects (non-agile) and let us assume that we know how to read the pulse of these projects.  Now, we want to measure the pulse of offshore agile projects. That is the topic.  How 'measuring the pulse' is going to be different here?  What are the differences or challenges? Why is this topic important?  These aspects are not coming out very well.  Yes, it is very challenging to articulate all these in an abstract of less than 100 words.   

    Here is my suggestion.  Please update your abstract  - you can make it 200 or 250 words.  Also, if you have a related slidedeck or other content please share.  That will be of great help to our reviewers and program committee members.

    Also, as I mentioned in the other proposal, please subtantiate  - write a line or two about the foundation/experience or incident or triggering point,   tell why.   That is going to pull the audience.

     

    Regards,

    Raja

    • Arijit Sarbagna
      By Arijit Sarbagna  ~  3 years ago
      reply Reply

      Hi Raja,

      Very well said & really appreciate this guidance. I will get this updated & tag the deck alongwith.

      Regards

      Arijit

  • Sudipta Lahiri
    By Sudipta Lahiri  ~  3 years ago
    reply Reply

    Hi Arijit,

    Is this the slidedeck for this session? I wasn't able to co-relate to the topic. The slides look very basic... 

    Pardon me if I am missing something.

    Regards

    Sudipta.

    • Arijit Sarbagna
      By Arijit Sarbagna  ~  3 years ago
      reply Reply

      Hi Sudipta,

      Apologies! That was a reference to a PMI Chapter presentation - nothing to do with the topic (I placed this link - as it was suggested that any other reference will also do).

      Regards

      Arijit


  • Liked Dinesh Sharma
    keyboard_arrow_down

    Thinking Environment - Do you have one?

    Dinesh Sharma
    Dinesh Sharma
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    Everything we do depends for its quality on thinking we do first. Our thinking depends on the quality of our attention for each other.

    A Thinking environment is the set of ten conditions under which human being can 'think' for themselves - with rigour, imaginaton, courage and grace. A Thinking Environment is natural, but rare. It has been squeezed out of our lives and organisations by inferior ways of treating each other.

    Thinking environment is based on ten behaviours that generate the finest thinking, and have become known as The Ten Components of a Thinking Environment. These components are

    • Attention,
    • Equality,
    • Ease,
    • Appreciation,
    • Encouragement,
    • Feelings,
    • Information,
    • Diversity,
    • Incisive Questions and
    • Place.

    Each Component is powerful individually, but the presence of all ten working together gives this process its transformative impact.

     

  • Liked Dinesh Sharma
    keyboard_arrow_down

    Offshoring Agile Projects - Myth, lies and Facts

    Dinesh Sharma
    Dinesh Sharma
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Offshoring in an agile environment (especially with Indian IT organisation) is always a hot topic within agile communities. You will often find people talk about challenges rather than opportunities with offshoring agile projects e.g.

    • communication challenge,
    • lack of focus on quality,
    • rigid offshore organisation environment,
    • lack of agile practice knowledge,
    • lack of trust etc.

    Although these constraint-cum-challenges often directly linked to offshoring but it can exists in a non-offshore environment as well. For example, to see how you can work effectively with distributed teams you don't need run a project in offshore environment, just split your teams and ask them to sit on a different floor without seeing each other face to face and all these so called offshore challenges will appear in an onsite environment as well.

    So lets understand various Myths, lies and facts about offshoring agile project and understand key ingredients to make it successful.