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.
Down with the
Revolution
hacking the hype and clearing a path
for agile business analysis
DavidJCMorris CSM CBAP ITCP
what do
agile practices
really mean for
business analysts ?
why am I here to talk about this ?
health warning
on with the show ...
agile
BA
DON’T PANIC
cutting through the
hype
a brief
lesson in grammar
“Most media today
report that Agile
has reached
mainstream usage”
“Most media today
report that agile
has reached
mainstre...
dictionary definition
ag·ile [aj-ahyl]
–adjective
1. quick and well-coordinated in movement; lithe.
2. active; lively.
3. ...
a brief
history of time
is this an agile revolution?
there will always be cowboys
use simple frameworks
a brief
debunking of hype
HYPE is a root cause
of antagonism
waterfall practices are bad
agile practices are on a spectrum
waterfall
‘rigid’
‘chaos’agile
iterative kanban
if you’re not doing XP or
pure Scrum you’re not agile
Snowbird, 2001
individuals beat processes
working software beats documentation
collaboration beats contracts
change beats plans
… we have...
oh, yeah, we’ve implemented Agile
already
Agile projects are just an excuse
for no discipline or planning
so if it’s
not a revolution,
what’s really changed ?
accepting uncertainty
shift happens
did the cat survive in the box ?
no plan survives first contact ...
new approach to risk
purpose of gates
gates on ‘waterfall’ projects
Analysis
Design
Development
Verification
Release
gates on agile projects
gates on agile projects
© 2010 International Institute of Business Analysis
value-driven
what is business value ?
Value-driven vs plan-driven
Plan-
driven
Value-
driven
Fixed Scope Resources Time
Waterfall Agile
Estimated ScopeResources...
one more thing
on agile projects, there is nowhere to hide.
A G I L E
what does it mean for
business analysts ?
the need for
agile business analysis
change in approach
roles for the
business analyst
Systems analysis
Requirements facilitation
Requirements ownership
Product owner (proxy)
business analysis
on agile projects
© 2010 International Institute of Business Analysis
closing
questions
Please note: no kittens were harmed in the making of this presentation
thank you
linkedin.com/in/DavidJCMorris
twitter.com/DavidJCMorris
david@DavidJCMorris.com
DavidJCMorris.com
Down with the revolution - hacking the hype and clearing a path for agile business analysis
Down with the revolution - hacking the hype and clearing a path for agile business analysis
Down with the revolution - hacking the hype and clearing a path for agile business analysis
Down with the revolution - hacking the hype and clearing a path for agile business analysis
Down with the revolution - hacking the hype and clearing a path for agile business analysis
Upcoming SlideShare
Loading in …5
×

Down with the revolution - hacking the hype and clearing a path for agile business analysis

467 views

Published on

Published in: Business, Technology
  • Be the first to comment

Down with the revolution - hacking the hype and clearing a path for agile business analysis

  1. 1. Down with the Revolution hacking the hype and clearing a path for agile business analysis DavidJCMorris CSM CBAP ITCP
  2. 2. what do agile practices really mean for business analysts ?
  3. 3. why am I here to talk about this ?
  4. 4. health warning
  5. 5. on with the show ...
  6. 6. agile BA
  7. 7. DON’T PANIC
  8. 8. cutting through the hype
  9. 9. a brief lesson in grammar
  10. 10. “Most media today report that Agile has reached mainstream usage” “Most media today report that agile has reached mainstream usage” “Most media today report that agile practices have reached mainstream usage”
  11. 11. dictionary definition ag·ile [aj-ahyl] –adjective 1. quick and well-coordinated in movement; lithe. 2. active; lively. 3. marked by an ability to think quickly; mentally acute or aware.
  12. 12. a brief history of time
  13. 13. is this an agile revolution?
  14. 14. there will always be cowboys
  15. 15. use simple frameworks
  16. 16. a brief debunking of hype
  17. 17. HYPE is a root cause of antagonism
  18. 18. waterfall practices are bad
  19. 19. agile practices are on a spectrum waterfall ‘rigid’ ‘chaos’agile iterative kanban
  20. 20. if you’re not doing XP or pure Scrum you’re not agile
  21. 21. Snowbird, 2001
  22. 22. individuals beat processes working software beats documentation collaboration beats contracts change beats plans … we have come to value … individuals and interactions over processes and tools working software over comprehensive documentation customer collaboration over contract negotiation responding to change over following a plan while there is value in the items on the right we value the items on the left more. Evil plans for world dominationAgile Manifesto
  23. 23. oh, yeah, we’ve implemented Agile already
  24. 24. Agile projects are just an excuse for no discipline or planning
  25. 25. so if it’s not a revolution, what’s really changed ?
  26. 26. accepting uncertainty shift happens
  27. 27. did the cat survive in the box ?
  28. 28. no plan survives first contact ...
  29. 29. new approach to risk
  30. 30. purpose of gates
  31. 31. gates on ‘waterfall’ projects Analysis Design Development Verification Release
  32. 32. gates on agile projects
  33. 33. gates on agile projects © 2010 International Institute of Business Analysis
  34. 34. value-driven
  35. 35. what is business value ?
  36. 36. Value-driven vs plan-driven Plan- driven Value- driven Fixed Scope Resources Time Waterfall Agile Estimated ScopeResources Time What will it cost to deliver this scope? What scope can we deliver? What’s highest value?
  37. 37. one more thing
  38. 38. on agile projects, there is nowhere to hide. A G I L E
  39. 39. what does it mean for business analysts ?
  40. 40. the need for agile business analysis
  41. 41. change in approach
  42. 42. roles for the business analyst
  43. 43. Systems analysis
  44. 44. Requirements facilitation
  45. 45. Requirements ownership
  46. 46. Product owner (proxy)
  47. 47. business analysis on agile projects © 2010 International Institute of Business Analysis
  48. 48. closing
  49. 49. questions Please note: no kittens were harmed in the making of this presentation
  50. 50. thank you linkedin.com/in/DavidJCMorris twitter.com/DavidJCMorris david@DavidJCMorris.com DavidJCMorris.com

×