ričardas kunevičius: strategy implementation sprint by sprint
TRANSCRIPT
Strategy implementationsprint by sprint
2
Content
• Situation– Scrumming for one year already– Current issues
• Strategy and direction• New portfolio concept and structure• Link to planning• 2 Conclusions
3
Company and me
• E-Bros– IT innovation company– Common business with partners– Investing into product development– Always looking for new opportunities and ideas
• Me– 20+ years in IT field– 10 years in big corporate business– 3 years at E-Bros
4
Scrum @E- Bros
5
SCRUM @ E-BrosOctober 2010 - August 2011
– 417 user stories– 1689 story points
6
Performance to compare
7
Main benefits
• Happy customers– Predictable short term delivery– Great involvement into the process
• Increasing of SW quality– Doing exactly what’s needed– Prompt feedback– Fast cycle
8
New challenges
• People– On the edge of chaos but not beyond
• Teams– Anarchy, federation, collaboration
• Products and platforms– Chicken or egg
• How to manage it all– Clear view, right direction
9
Strategy
• From businessdictionary.com:– “A method or plan chosen to bring about
a desired future, such as achievement of a goal or solution to a problem”.
• www.thefreedictionary.com– Synonym for planning!
• All about a way how to be where we want to be
10
Project portfolio as a strategy reflection
11
Why it doesn’t work with SCRUM
• Wrong approach– Project isn‘t a list of stories– Project requires change tracking– Project has different acceptance criterion– And so on
• Well managed portfolio became useless– Broken down just in a month– Sprint by sprint rally– Targets and directions somewhere between the
lines
12
Project portfolio and SCRUM
13
New (old) portfolio concept: areas
14
New portfolio concept: targets
15
New portfolio concept: backlog
• For each target– User story for each step– Incremental value per user
story
16
New portfolio concept: user story
• User stories with size, priorities and status– Level of details on the backlog depends on
time– Keep just a short description for future
stories– More details just before development
• One story could be attach to a few targets
17
All together now!!!
Areas
Area1Target1Target2
Area2Target1Target2
Area3Target1Target2
Balance
Area1/Target 1
DefinitionAcceptance CriteriaDeadlineStatus
Value!!!
User story 1 Status SizeUser story 2 Status SizeUser story 3 Status SizeUser story 4 Status Size
Target backlog Execute!!!
Quarter planResource (team) allocationUser Stories
Keep it rolling!!!
18
Quarter plan
• Stories to select– A list of user stories for targets to be completed during
the quarter is compiled– + Future targets (from next 2 quarters)
• To avoid just one quarter horizon
• People to mobilize– Team involvement is needed– Review story points per area– Evaluate the workload
• Go back for the targets if unreachable
– Allocate teams for the quarter
19
Control of the process• Strategy meetings
– 2-3 times a year– To review areas and directions– Check the target achievement– Set up the new targets/cancel some of them
• Quarter planning– Once per quarter– Review performance and share experience– Review backlogs per area for the quarter
• Check if all the items still valid• Check if we could do this
20
Along the strategy
Areas
Targets
Backlog
Strategy planning
Quarter planning
21
Conclusions
• Scrum implementation direction– Doesn't matter– It’s most effective when all tears are covered
• Transparency &Commitment– Information flow– Common goals (targets)– Commitment at all levels
• End right before the end– “All wrong but some useful”
22
That is all - thank you very much