The document outlines changes to the development process including using a common technology stack across teams to reduce duplicate work, implementing sprints for planning and estimating work, and continuing strengths while ensuring any process changes do not disrupt developers' daily work. Sprints will be two weeks long and include estimated points for bugs and chores, with developers planning their own sprints in consultation with project managers and leads. Retrospectives will also be used to evaluate the process.
2. • We are doing very well as a great team
• Continue our strengths
3. • Guiding principle:
No change to Devs day-to-day work.
If there is any, we have to look at it any fix it.
4. Pivotal
• Common stack on impending work across Delhi & SF.
– Probability of similar effort reduced in two places.
• Visibility of prioritized work.
• Ability to choose work.
• Some predictability of delivery.
5. Sprints
• Sprint Plan – Dev for himself.
– In consultation with PM/EM/Lead
• Estimation : 2SP = 1 day
– Predictability of delivery
• Sprint:
– 2 week sprint.
– Bugs/Chores having points
– Estimation scale 0-10, 20
• Retrospective.
