Continuous software dev cycle- the Pros

News

Currently we are heads down in a complex software transformation project w/ a large leader in the renewable energy space. Here is what has worked great:

  1. On Friday we deliver last week's project and plan for next week with client's stakeholders (PM, tech lead, etc).
  2. On Sunday night I talk w/ my Vietnam team's technical PM and plan for next week. We also do a retrospective for previous week.
  3. On Monday morning I catch up w/ my Vietnam tech PM and go over previous day's progress as well as record any question the team may have for client.
  4. I then jump on a half hour call w/ client to update her on the project's progress. We also figure out roadblocks and adjust priorities for this week's tasks.
  5. Client's dev team merges Vietnam team' code and starts developing throughout the day. Before they leave they commit and do a PR.
  6. On Monday's evening (PST) I talk to my Vietnam tech PM and give him tasks for the day (Tuesday Vietnam time).
  7. Vietnam team has daily standup w/ the tech PM, merges the PRs and starts a new day.
  8. Rinse and repeat.

It has been working really well. The client is happy as we are 2x their dev speed. Since we deploy and do PRs daily the client can provide feedbacks right away. Plus the team has been super diligent in providing estimates, diagrams and documentations. Plus any ticket gets prioritized and solved as soon as we can. There are some challenges however, which I'll cover in the next post.

LET'S GET STARTED

Get A Quote Now

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.