transitioning to agile (oy!) judith sol dyess
Aug 16, 2015
transitioning to agile
(oy!)
judith sol dyess
agile experience to date
3 months in agile project environment
1 launched project
3 inceptions
1 retrospective
4 active projects (including maintenance work)
pretty new at this!
what does “agile” mean to you?
we’ll focus on…
collecting requirements
estimating
budgeting
how do you collect requirements?
- listen and ask questions
understand the problem
the most important thing you do is
you own this
the master story list
stories: how are we building this?
* the right level of detail
the master story list
the master story list
points: how much effort?
* this is a range
STORIES
estimating
velocity: how fast?
* this is a team average after ~3 iterations
estimating
iterations: how long? how often
* showcases, IPM, retros…
points aren’t always “it”
estimatingdesign(oy!)
estimating
when you put it all together
you have an estimate
“and that’s what it’s all about”
– every client ever
“…how much is it going to cost?”
agile & risk
estimates will change
you get flexibility through iterations
why? to move fast and adapt as needed
my take-aways
points are still confusing but…
estimates are awesome if you communicate well
risk is minimized if you communicate well
agile can succeed if you communicate well
cost | scope | schedule: you still can’t get all three :(
did you catch that communication part?
helpful resources
Jonathan Rasmusson The agile samurai: how agile masters deliver great software
Michael Cohn Agile estimating and planning
Michael Cohn User stories applied: for agile software development
Esther Derby Agile retrospectives: making good teams great
thank you :)
questions?