1 - Agile in a nutshell

2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements changes. Delivers small amount of new features at each iteration ). Fixed timebox (2 to 4 weeks) ●Understanding and adapt to customer business through frequent and regular deliveries of working versions of products to end users or a representative ●Requires a a day-to-day team collaboration, with embedded marketing (product owner). Decision makers are different: ●the product owner makes decisions about the product goals, ●the team collaboratively decides how to achieve the product goals ●Needs to automate as much as possible the test activities. The efficiency of the teams depends of the effectiveness of the tool set

3 - Impact on project management ●Continuous (re) planning throughout the project : to manage evolutionary deliveries ●Fixed cost & schedule for each iteration: the content is adapted to the schedule ●Continuous testing: to master quality of each delivery to end user Version n Build, Test … n + 1n + 2 Plan driven Traditional Agile Value driven CostScheduleFeatures RequirementsCostSchedule Estimates Constraints

4 - Simple Complex Anarchy Complicated Technology Requirements Far from Agreement Close to Agreement Close to Certainty Far from Certainty People Complex Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle. Agile Project noise level

5 - Scrum Framework Product owner ScrumMaster Team Roles Sprint planning Sprint review Sprint retrospective Daily scrum meeting Ceremonies Product backlog Sprint backlog Burndown charts Artifacts