Tag Archives: Sprint

How do you handle Sprint review and retrospective for multiple Scrum teams?

If there are multiple teams working off of one Product Backlog, how best to reflect and close the iteration? I see these choices: choice 1: one review per team one retrospective per team one consolidated review for everyone at end choice 2: one consolidated review one retrospective per team choice 3: one consolidated review one consolidated retrospective I have a bias to the last choice, if space is not a factor. What is yours? Do you prefer another way to coordinate these meetings? Here are my definitions for these Scrum ceremonies. Sprint Review: Story time. Only stories which are DONE … Continue reading

#agile explained | Tagged , , , , , | Comments Off on How do you handle Sprint review and retrospective for multiple Scrum teams?

Whole Team Incentives – Redeeming Features for Rewards

After VYC2.0 launched, I was asked who were the heroes in the group. The one or two people who deserved recognition for all of their hard work. I was hunting around for the email chain, but I’m pretty diligent about deleting emails. I wish sometimes I wasn’t so relentless at that, but I don’t have it. Essentially, I responded that calling out a couple of people creates competition, that everyone stepped up and deserves to be recognized. Management agreed, and everyone involved wound up with a Flip, and I was asked how we may be able to codify some whole … Continue reading

#agile explained | Tagged , , , , , | Comments Off on Whole Team Incentives – Redeeming Features for Rewards

Setting a Minimum Bar for Scrum

At one of our Program Management meetings, I was asked what was absolutely necessary to do for Scrum and Sprints. I was very reticent to write up a check-list of what is needed as it will always have a prescribed, controlling feel to enforce how to work. Using a cheat-sheet like this can leave short that full understanding, of being able to grok Agile. There is so much more to it, and so very much that has been left out, or could be misinterpreted. Yet I wound up writing it. Our group is so distributed and the team was asking … Continue reading

#agile explained | Tagged , , , , , | Comments Off on Setting a Minimum Bar for Scrum

Kanban Ground Rules Example for a Specific Team

Kanban System for Software Engineering Kanban System for Software Engineering – KSSE Introduction Definitions Roles Acronyms Metrics Queue sizes Process Getting Things into TIP and on through to production Self-organization Get Things Done Releasing Constraints Other Interesting Work Kaizen Generating and Verifying Acceptance Criteria Stand-up Measures of Success Visual tracking Tradeshow For Finished Features Retrospective Regular Cadence Whole Team Incentives Introduction Kanban (in kanji where kan, means “visual,” and ban, means “card” or “board”) is a concept related to lean and just-in-time (JIT) production. Kanban is a signaling system. As its name suggests, Kanban historically uses cards to signal the … Continue reading

#agile explained | Tagged , , , , , , , , | 3 Comments