Should a technical issue be a User Story in the Product Backlog? How Agile teams can handle system tech problems within Scrum.
Scrum by Example
Scrum By Example – Waiting Too Long to Create Acceptance Criteria
How, when, and why to write your acceptance criteria of User Stories for Sprint Planning. Case study of an Agile Scrum team, with practical examples.
Scrum By Example – Story Splitting Fun
Case study with practical examples how to write good Scrum User Stories by story splitting. Keep stories brief and from end user’s point of view.
Scrum By Example – Learning How to Estimate
Learn how to Estimate in Agile Scrum for Sprint Planning and Backlog Grooming/Refinement Sessions. The value of Planning Poker™ and blind estimates.
Scrum By Example – New People on the Team
Hiring, adding, or changing a Team member in Scrum means the whole Scrum team has to adjust. How a ScrumMaster can help during transition, and problems to avoid.
Scrum By Example – The Team Learn How to Learn
A Standup report leads our case study ScrumMaster to arrange for his Scrum team to use Coding Dojos to build confidence and pay down Technical Debt.
Scrum by Example – Stop Digging New Holes
Our case study Scrum Team is accumulating Technical Debt and needs to adjust Velocity and review Definition of Done, Unit Testing and Restructuring Legacy Code.
Scrum By Example – Technical Debt is Slowing the Team
Our ScrumMaster pulls up the CFD for the current release… and notices that the rate at which stories are being selected has slowed down in the past few sprints.