Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum Australia 2014 - Drive Project Success in Only 1 Week


Published on

Juliano walks through a lean agile approach to incepting a product, all within 1 week.

Published in: Technology
  • Be the first to comment

Scrum Australia 2014 - Drive Project Success in Only 1 Week

  1. 1. Drive project success in only 1 week Juliano Bersano
  2. 2. Why ‘looking agile’ is very different from ‘being agile’
  3. 3. Have you ever been in a project that looks agile, but… • People can't articulate a unified objective and vision • No link between story priorities and business objectives • No part of scope is negotiable without a change request • Team members are told what and how to do it • Plans are used as commitments • IT and Business still work in silos • Team members don’t discuss cost/benefit
  4. 4. Why does that happen? • A sense of purpose and team hasn’t been created • Clear business drivers are not used for prioritisation • Team members don’t fully understand context • No team ownership or empowerment • People haven’t fully bought into the initiative • The way you start a initiative shapes expectation, mindset and behaviour throughout
  5. 5. How Agile Inception drives project success (a.k.a. Initiation, Initiate, Discovery etc.) • Setting a new way of working and expected behaviour • Defining shared vision and business objectives • Setting foundation for future scope discussions • Setting example of how team will work together • Setting expectation of collaboration and ownership • Creating a solution together • Creating a shared plan that people buy into • Doing it all together as a team
  6. 6. Basic outputs of an Agile Inception • Prioritised business drivers • Prioritised list of user stories • Release Plan
  7. 7. Outcomes of an Agile Inception By discussing it: Shared understanding among stakeholders and team By building it together: Sense of ownership of solution and plan
  8. 8. The basic flow of an Agile Inception Setting the Context Background Business Drivers Ways of Working Getting to User Stories User Flows Technical Landscape User Stories Planning the Release Release Prioritisation Estimation Release Planning
  9. 9. Setting it up for success  Team members allocated and ready  Product Owner assigned  Key stakeholders available  Dedicated room with lots of wall space booked  Workshops booked and planned  Lots of post-its, sharpies, butchers paper, whiteboard  Core Inception team with facilitators ready
  10. 10. 1-week agenda for Agile Inception • Sessions of 2- 3 hours in the morning and afternoon • Daily consolidation of output • Core Inception team works before and after sessions
  11. 11. Background 1. Why are we doing this? 2. What do we expect to improve? 3. What are the constraints? Outcome Understand motivation and context
  12. 12. Outcome Business drivers (primary, secondary and tertiary) Business Drivers
  13. 13. Business Drivers 1. Brainstorm business drivers 2. Discuss, group and discard 3. Prioritise in: a) Primary b) Secondary c) Tertiary Outcome Business drivers (primary, secondary and tertiary)
  14. 14. Ways of Working 1. Discuss what it means to be Agile 2. Discuss cadence and ceremonies: • Daily stand up time • Sprint start and finish • Sprint Planning time • Sprint Review/Demo time • Retrospective time 3. Discuss who is expected to attend Outcome Agreed cadence, ceremonies and attendance
  15. 15. Outcome Sketched user flows User Flows
  16. 16. User Flow 1. Identify key users 2. Sketch ‘happy path’ user flow 3. Sketch alternative flows 4. Sketch screen detail (if it helps understand user stories) Outcome Sketched user flows
  17. 17. Outcome List of user stories User Stories
  18. 18. Outcome List of user stories User Stories
  19. 19. User Stories 1. Identify user stories in each user flow 2. Walk group through it 3. Identify gaps 4. Break down further where necessary Outcome List of user stories
  20. 20. Outcome High-level solution options Technical Landscape
  21. 21. Technical Landscape 1. Whiteboard systems involved and architecture 2. Discuss constraints, dependencies and risks 3. Agree on high-level solution approach and options Outcome High-level solution options
  22. 22. Outcome Prioritised user stories in (and out) of release Release Prioritisation
  23. 23. Release Prioritisation 1. Prioritise user stories, considering business drivers 2. Agree minimum release scope to achieve business objectives Outcome Prioritised user stories in (and out) of release
  24. 24. Outcome Estimated stories and velocity estimate Estimation
  25. 25. Estimation 1. Estimate relative size of user stories 2. Estimate team velocity per sprint Outcome Estimated stories and velocity estimate
  26. 26. Outcome Release Plan Release Planning
  27. 27. Release Planning 1. Define uncertainty buffer (%) with PO 2. Discuss ramp up period 3. Discuss stabilisation period 4. If scope-bound: a) Add up total points for release + bufffer b) Determine total sprints needed to finish the release 5. If time-bound: a) Determine total sprints and total capacity available b) Assign prioritised stories up to total capacity - buffer Outcome Release Plan
  28. 28. Other activities that may be used • Ice breaker/warm up • Elevator pitch • Product in a box • Futurespective • Cover story • 6-8-5 • Trade-off sliders • Anchors & Engines • User story mapping • “As-is” process/painpoints • Risk matrix etc.
  29. 29. Characteristics of an Agile Inception workshop • Well-prepared: it is set up for success and well-planned • Intense: it is a lot of work and covers a lot of ground • Focused: clear steps leading to an outcome • Representative: key stakeholders and team members present • Decisive: Product Owner deciding on the spot • Hands-on: it is real work and not a presentation • Collaborative: people build the solution and plan together • Fun: people enjoy working together towards an objective • Unifying: it brings people together as one team
  30. 30. Summary • To work in an agile way, you must start in an agile way • Kick it off with workshops (where we work on it) rather than presentations (where we are told about it) • Agile Inception is part of taking people through a journey and forming a team • Agile Inception requires less effort and less time than doing it the traditional way • Sense of ownership is one of the most important outcomes of an Agile Inception
  31. 31. Thank you! Juliano Bersano 0403 531 051