Increasing Agile/Scrum
Adoption

Why?

Increase Productivity of the Dev/QA team, more work satisfaction from devs/QA, increased overall value, so that our products can:

• Engage more patients
• Reduce nurse time
• Build innovative care models
• Serve as many patients as possible
• Decrease down time
• Increase utilization

What?

Further implement scrum fundamentals in order to:

• Engage more patients
• Reduce nurse time
• Build innovative care models
• Serve as many patients as possible
• Decrease down time
• Increase utilization

How?

• Split into 3 smaller teams of 7-8 ppl
• Teams to include FE, BE, Testers (cross-functional)
• Each team to have their own scrum ceremonies
  • Sprint Planning, Retro, etc.
  • More time to discuss the work that applies to them when the team size is smaller

1 - Smaller teams

How?

• Each team to incorporate a story grooming meeting
  (1-2hrs per week) 
• Includes every member of the scrum team (FE, BE, QA, PO)
• Fully define and understand acceptance criteria for every ticket/story (creates clean runway)
• Clearly understand the business value of every ticket
• Size each ticket as a team (more accuracy)
  • Leverages the brain-power of the every team member
• Accurate ticket sizing = sprint capacity management/protection and better predictability

2 - Modify Story Grooming

How?

• Tickets to be developed and tested within the same sprint. 
• Shortens feedback loop
• Helps teams understand capacity better, predict velocity better
• Less context-switching for dev teams
• Required: smaller, well-defined tickets that provide clean runway for developers/testers

3 - Inflexible Sprint Time-Box

How?

• Individual story demos for each ticket to PO for acceptance
  • Encourages narrower more focused feedback loop
  • Requires clear acceptance criteria of each ticket
• End of sprint showcase to stakeholders, PO, UX, Client Success, Support, etc.
  • Encourages a wider feedback loop and increases awareness

4 - Encourage feedback loop