Scrum Australia 2014 - Drive project success in only 1 week
pragmateam
9 views
31 slides
Sep 09, 2024
Slide 1 of 31
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
About This Presentation
Juliano walks through a lean agile approach to incepting a product, all within 1 week.
Size: 2.65 MB
Language: en
Added: Sep 09, 2024
Slides: 31 pages
Slide Content
Drive project success in only 1 week Juliano Bersano www.pragmateam.com.au
Why ‘looking agile’ is very different from ‘being agile’
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
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
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
Basic outputs of an Agile Inception Prioritised business drivers Prioritised list of user stories Release Plan
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
The basic flow of an Agile Inception
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
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
Background Why are we doing this? What do we expect to improve? What are the constraints? Outcome Understand motivation and context www.pragmateam.com.au
Outcome Business drivers (primary, secondary and tertiary) Business Drivers www.pragmateam.com.au
Business Drivers Brainstorm business drivers Discuss, group and discard Prioritise in: Primary Secondary Tertiary Outcome Business drivers (primary, secondary and tertiary) www.pragmateam.com.au
Ways of Working Discuss what it means to be Agile Discuss cadence and ceremonies: Daily stand up time Sprint start and finish Sprint Planning time Sprint Review/Demo time Retrospective time Discuss who is expected to attend Outcome Agreed cadence, ceremonies and attendance www.pragmateam.com.au
Outcome Sketched user flows User Flows www.pragmateam.com.au
User Flow Identify key users Sketch ‘happy path’ user flow Sketch alternative flows Sketch screen detail (if it helps understand user stories) Outcome Sketched user flows www.pragmateam.com.au
Outcome List of user stories User Stories www.pragmateam.com.au
Outcome List of user stories User Stories www.pragmateam.com.au
User Stories Identify user stories in each user flow Walk group through it Identify gaps Break down further where necessary Outcome List of user stories www.pragmateam.com.au
Technical Landscape Whiteboard systems involved and architecture Discuss constraints, dependencies and risks Agree on high-level solution approach and options Outcome High-level solution options www.pragmateam.com.au
Outcome Prioritised user stories in (and out) of release Release Prioritisation www.pragmateam.com.au
Release Prioritisation Prioritise user stories, considering business drivers Agree minimum release scope to achieve business objectives Outcome Prioritised user stories in (and out) of release www.pragmateam.com.au
Outcome Estimated stories and velocity estimate Estimation www.pragmateam.com.au
Estimation Estimate relative size of user stories Estimate team velocity per sprint Outcome Estimated stories and velocity estimate www.pragmateam.com.au
Outcome Release Plan Release Planning www.pragmateam.com.au
Release Planning Define uncertainty buffer (%) with PO Discuss ramp up period Discuss stabilisation period If scope-bound: Add up total points for release + bufffer Determine total sprints needed to finish the release If time-bound : Determine total sprints and total capacity available Assign prioritised stories up to total capacity - buffer Outcome Release Plan www.pragmateam.com.au
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.
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
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