Ergebnisse zu Ihrer Suche: event

E.g., a Daily Scrum can be a Morning-Reporting-Meeting or an event of self-management. That’s up to us team members. The same applies to SAFe: The PI Planning can generate a Gantt Chart. But it also can be a great collaborative refinement of a Product Backlog. It depends on us. A rant like “SAFe: A Waterfall Pig with Agile Lipstick” shows how this also works in the opposite.

Roles, events and artifacts are…nice. SAFe is a dual organization. This is often not clear at first glance and later causes confusion. Malicious tongues claim that this dual organization is there to cause confusion. But it is actually quite simple: On the right is the old, familiar thing. Left is the new thing.

This is based on several assumptions: The length of an Iteration/Sprint is 2 weeks (which leaves us with 10 working days); 10% of our time is spent on Iteration/Sprint events (as suggested in the Scrum Guide); 10% of our time is spent on Product Backlog Refinement (as suggested in earlier versions of the Scrum Guide); Our reference Story, which represents “1” Story Point, takes about half a day to

SAFe uses 8 Story Points per developer for a 2 week Sprint, or more generally 0.8 Story Points per workday. 0.8 Story Points per workday take into account the time spent for the Sprint events and Refinement. Another option to determine the Capacity for the first Sprint/Iteration would be to select Stories for the Sprint and then to count the number of Story Points. You can choose either way.

Der Lösungsansatz von LeSS ist es, den Sprint-Zyklus von Scrum zu belassen, aber bestimmte Scrum-Events gemeinsam durchzuführen. Bei LeSS werden die Sprint Planung Eins und das Sprint Review gemeinsam durchgeführt. Jedes Team hat seine eigene Retrospektive und darüber hinaus gibt es eine gemeinsame Retrospektive mit Vertretern aller Teams.