1

Reminders on Scrum and Agility

• Agility, another vision.
• Roles and artifacts. Ceremonies.
• Additional contributions (Lean, XP, etc.).

2

Product Owner activities

• Clarify the statement of needs.
• Plan based on business value.
• Accept or reject the product.

3

Statement of needs

• Develop a vision. Themes, roles.
• User Story quality and calibration.
• Maturity level of a User Story ("Ready" User Story).
• Product backlog: defects and technical stories. How to prevent bugs from accumulating?
• Backlog ordered first. Emerging specifications. Automate acceptance tests.

4

Organisation and collaboration in a Sprint

• Iteration planning. Fixed content, change.
• Carefully prepare and lead the Scrum Meeting so that it is effective. Iteration management by Kanban.
• Self-organisation review, role of the Scrum Master.
• Developments aligned with technologies rather than use cases: difference between a task and a story.
• Presence of the business representative, demo at the end of each iteration. Role of the Product Owner.
• Improve the retrospective, make better use of sprint debriefs.

5

Agile planning

• The four levels (roadmap, version plan, etc.).
• Basic principles. From the infernal triangle to the virtuous square. Establish a sustainable pace for all.
• How to react if the prioritisation of User Stories does not take development constraints into account?

6

Other advanced points

• Effort points versus person-days. Planning Poker, estimate based on similarity. Estimate stories and features.
• Tools for statements of needs, planning and visual management.
• Reporting: burndown charts, burnup charts, other indicators.
• The application does not pass the tests. Organisation to fix bugs (Stop the line).
• The four rules of simple design. Test-Driven Development.