Liam Sheerin - Agile Development

12
Agile development Liam Sheerin Head of Engineering and Project Management S3UG May 2010

Transcript of Liam Sheerin - Agile Development

Page 1: Liam Sheerin - Agile Development

Agile development

Liam SheerinHead of Engineering and Project ManagementS3UG May 2010

Page 2: Liam Sheerin - Agile Development

About this sessionDemonstrate agile development

Brief introduction to agile development

Set a scenario with which we'll create a site using agile methods

Your input used to prioritise site features

Develop then present the site at the end of the day

Page 3: Liam Sheerin - Agile Development

Brief introduction to Agile

Page 4: Liam Sheerin - Agile Development

Brief introduction to AgileLightweight project management and development framework

Requirements and solutions evolve through collaboration

Often used when requirements are unknown or likely to change over time

'Just-in-time' analysis means no big up-front design phase

Page 5: Liam Sheerin - Agile Development

Brief introduction to Agile

Product Vision devised to describe the product: customer, their needs, benefits, product name, differentiators

Features are prioritised into a Product Backlog by the Product Owner

Projects are broken down into two to four week iterations called sprints

Page 6: Liam Sheerin - Agile Development

Brief introduction to AgileDevelopment takes place in sprints against a sprint backlog

Sprint backlog is a prioritised list of features taken from the Product Backlog

Sprints aim to provide fully complete functionality

Potentially shippable product after each sprint

Page 7: Liam Sheerin - Agile Development

Brief introduction to Agile

Page 8: Liam Sheerin - Agile Development

The Product BacklogThe Product Backlog is a list of features/user stories NOT a large detailed specification

Features in the Product Backlog can be amended and reprioritised throughout the project(Backlog Grooming)

Page 9: Liam Sheerin - Agile Development

The Product BacklogEach feature is attributed with story points detailing the relative complexity of the feature: 1 (small), 2 (medium), 4 (large), 8 (extra large)

Story points are used describing complexity rather thanduration

Page 10: Liam Sheerin - Agile Development

The Sprint BacklogThe Sprint Backlog is the subset of the Product Backlog that will be worked on during the Sprint

Each Sprint can work on a predefined number of story points

Detail added to featuresin sprint planningmeeting

Page 11: Liam Sheerin - Agile Development

Agile summaryAgile focuses on moving quickly and is a lightweight methodology

List of features rather than large specification

Just-in-time analysis

Each sprint aims to provide a shippableproduct

Page 12: Liam Sheerin - Agile Development

Brief introduction to Agile