Reflection – Learning Launch

Challenge:

I am the Scrum Master for a multimillion-dollar project and my challenge is to improve the  velocity, streamline the process and increase the revenue for my organization. The project scope  includes developing online collaborative platform for suppliers and vendors.

•  The execution model is based on Agile principles where there are 5 scrum teams situated  in different geo locations, responsibility is split among 3 different vendors.

•  The project is based on fixed cost agreement and I need to bring the revenue margin to  60% for my organization

•  Improve the Collaboration for the distributed scrum teams considering the time zone  difference and cultural distributions.

•  The feature development should go live every 2 weeks and maintaining a balanced  distribution of working hours among the team members.

We will focus on discovering the ineffectiveness and problematics areas for our team members,  as well as key stakeholders.

Selection:

We went through several internal discussions and the design thinking activities, tools and  principles. As there is no proven method of universal success and every unique problem need to  come up with a unique solution, we decided to try the “Learning Launch” tool which is based on  experiment quickly and identify if it works for us or not.

Application:

Learning Launch 1:

We focused on the structure/execution of the “Delivery Model” of our tasks and procedures. More  specifically we wanted to focus more on the “Team Structure” and the “Process” considering the  distributed scrum teams. We adapted to the Agile release train principle with different agile PODs  located at different geo locations. We made sure that there is an overlap of time zone for certain  hours for handover. We brought in our Agile Coach to review the idea and have a workshop with  the team to ease out the huddle and bring the team on the same page. We created a guideline  with clear description of our new process, established the RACI, Understand the roles &  responsibilities.

With the help of the higher management we were able to build a specific training and leering  center specific for our project. We identified a good mix of senior and junior team who can deliver

with high quality and maintaining the right balance of revenue. We also created a SWAT team  who acts as backfill the absence of some team members to negate the impact of the delivery.

Learning Launch 2:

In the phase 2 we focused on the results of the tested idea after a span of 6 weeks. We collected  the anonymous feedback from our development team and the key stakeholders to know more  about the new process, understanding, concerns, improvements/suggestions. Apart from this we  hired an external consultant to review our proposed solution and the execution model.

With the help of the feedback and review we implemented few more tools and processes like:

•  Communication Channel for better collaboration

•  KPI audit templet

•  Use the baseline velocity for release planning

•  OKRs on quarterly basis, governance check points & remediation

•  Brought in few engineering best practices like “TDD, Code Reviews, Continuous  Integration, In-built Test Automation, CI CD full stack services built in”

Insight:

The application of the Learning Launch tool helped us identify assumptions and test the same. In  addition to this we analyzed the anticipated results to find that the new structure and process  would help us in long run. This will bring in transparency, productivity improvement and a cross  functional team. We did exceed in the actual results in terms of anticipated team Velocity, Revenue  margin and collaboration.

In future as a continuation process we will review in periodic basis and apply the Learning launch  designs. The ongoing implementation is beneficial at this stage, as results come before a full  rollout in the design thinking timeline.

Approach:

Knowing that our team has gone through several design thinking activities/tools and are at this  stage in the timeline based on the outcome of results during the test we understood that the  learning launch is the appropriate tool for us at this situation. As mentioned earlier, will review the  insight gained from our launches and incorporate the insight into future launch designs. Future  launch designs should reflect insight gained, progress made, and come closer to a compelling  solution ready for full rollout.

Thanking You    Mithilesh Gupta  lowetyler@hotmail.com


Reflection – Learning Launch Challenge : I am the Scrum Master for a multimillion - dollar project and my challenge is to improve the velocity , streamline the process and increase the revenue for my organization . The project scope includes developing online collaborative platform for suppliers and vendors . • The execution model is based on Agile principles where there are 5 scrum teams situated in different geo locations , responsibility is split among 3 different vendors . • The project is based on fixed cost agreement and I need to bring the revenue margin to 60 % for my organization • Improve the Collaboration for the distributed scrum teams considering the time zone difference and cultural distributions . • The feature development should go live every 2 weeks and maintaining a balanced distribution of working hours among the team members . We will focus on discovering the ineffectiveness and problematics areas for our team members , as well as key stakeholders . Selection : We went through several internal discussions and the design thinking activities , tools and principles . As there is no proven method of universal success and every unique problem need to come up with a unique solution , we decided to try the “ Learning Launch ” tool which is based on experiment quickly and identify if it works for us or not . Application : Learning Launch 1 : We focused on the structure / execution of the “ Delivery Model ” of our tasks and procedures . More specifically we wanted to focus more on the “ Team Structure ” and the “ Process ” considering the distributed scrum teams . We adapted to the Agile release train principle with different agile PODs located at different geo locations . We made sure that there is an overlap of time zone for certain hours for handover . We brought in our Agile Coach to review the idea and have a workshop with the team to ease out the huddle and bring the team on the same page . We created a guideline with clear description of our new process , established the RACI , Understand the roles & responsibilities . With the help of the higher management we were able to build a specific training and leering center specific for our project . We identified a good mix of senior and junior team who can deliver with high quality and maintaining the right balance of revenue . We also created a SWAT team who acts as backfill the absence of some team members to negate the impact of the delivery . Learning Launch 2 : In the phase 2 we focused on the results of the tested idea after a span of 6 weeks . We collected the anonymous feedback from our development team and the key stakeholders to know more about the new process , understanding , concerns , improvements / suggestions . Apart from this we hired an external consultant to review our proposed solution and the execution model . With the help of the feedback and review we implemented few more tools and processes like : • Communication Channel for better collaboration • KPI audit templet • Use the baseline velocity for release planning • OKRs on quarterly basis , governance check points & remediation • Brought in few engineering best practices like “ TDD , Code Reviews , Continuous Integration , In - built Test Automation , CI CD full stack services built in ” Insight : The application of the Learning Launch tool helped us identify assumptions and test the same . In addition to this we analyzed the anticipated results to find that the new structure and process would help us in long run . This will bring in transparency , productivity improvement and a cross functional team . We did exceed in the actual results in terms of anticipated team Velocity , Revenue margin and collaboration . In future as a continuation process we will review in periodic basis and apply the Learning launch designs . The ongoing implementation is beneficial at this stage , as results come before a full rollout in the design thinking timeline . Approach : Knowing that our team has gone through several design thinking activities / tools and are at this stage in the timeline based on the outcome of results during the test we understood that the learning launch is the appropriate tool for us at this situation . As mentioned earlier , will review the insight gained from our launches and incorporate the insight into future launch designs . Future launch designs should reflect insight gained , progress made , and come closer to a compelling solution ready for full rollout . Thanking You Mithilesh Gupta lowetyler@hotmail.com