Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Agile for Business Advantage Creoss 2 of 2

585
views

Published on

Agile for business advantage part 2 of 2 by Creoss

Agile for business advantage part 2 of 2 by Creoss

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
585
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 1
    Agile for Business Advantage
    Part 2 of 2
    Brian Boelsterli
    CREOSS Business Solutions
    September, 2010
  • 2. 2
    Agenda
    Setting the stage
    Where did the data for this presentation come from?
    Challenge / Technique
    Looking at the Top 10 list
    Techniques for addressing challenges
    Summary
    A recipe to consider
  • 3. 3
    Setting the stage
    Overwhelming amount of information on Agile adoption(Agile challenges)
    This presentation focuses on our experiences, our convictions
    What follows comes directly:
    From experience (over 10 years) in
    implementing ALL Agile projects (over 125),
    across major vertical markets (over 9),
    across a variety of team sizes (6 to over 400),
    across multiple technology realms (purely Microsoft, ubiquitus/mixed, purely Open Source, Legacy development and/or modernization),
    spanning team structures (co-located/local to international/disbursed)
  • 4. 4
    Agile challenges
  • 5
    Challenge: Business / IT Alignment
    • Today’s Agile methodologies do not directly address alignment between business imperative and technology initiative
    • 10. http://nevermindthebusiness.blogspot.com/: The evidence is damning. IT is failing to meet the needs of the Business. The business does not trust IT, and it's gradually taking control of technology itself, more and more. IT must change or be left behind......
    • 11. An ISACA study last year, "Changing Business Needs and Unmet Expectations Are Leading Causes of Technology Project Failure", revealed that nearly half of the Organizations surveyed have ended technology projects prematurely, with the top two reasons being that business needs had changed (29.9 percent) and the project did not deliver as promised (23.4 percent).
  • 6
    Challenge: Business / IT Alignment
    Top right quadrant is the goal of effective and aligned
    Does the software delivered improve value of any kind to the stakeholders?
    Key point: todays Agile techniques do not address Business/IT alignment
    http://sloanreview.mit.edu/the-magazine/articles/2007/fall/49102-1/the-path-to-itenabled-growth/
  • 12. 7
    SOURCE: Agile Unplugged/Creoss Business Solutions
    Technique: Business / IT Alignment
    • Portfolio brings Agile to better alignment
    • 13. If doing Scrum, look for the “Scrum of Scrums” in your approach OR adopt a more advanced Agile approach
    • 14. Incorporates Portfolio and KPI as part of its core principle
    • 15. http://sloanreview.mit.edu/the-magazine/articles/2007/fall/49102-1/the-path-to-itenabled-growth/: “Contrary to conventional wisdom, the path to IT-powered growth lies first in building high effectiveness and only then ensuring that IT projects are highly aligned to the business”
    • 16. Artifacts which specifically tie Corporate Objective to IT Strategy to IT Initiative
    • 17. Key point: awareness of being portfolio versus project-driven
  • 8
    Challenge: Adoption
    SOURCE: Agile Unplugged/Creoss Business Solutions
    Current average “heartbeat” is 2-4 weeks; too long?
    Adaptation intervals (retrospectives) of 2 to 4 weeks lengthens the adoption curve significantly
    Inspection intervals (demos) of 2 to 4 weeks lengthens the potential for things to go wrong and money to be spent
    Transparency intervals (planning and standups) of 2 to 4 weeks increases potential for risk to permeate the projects/initiatives
    Key point: Heartbeat has significance on Agile adoption
  • 18. 9
    Technique: Adoption
    4 week cycles
    1 week cycles
    Shorter cycles/iterations
    Transparency, Inspection and Adaptation occur more frequently ==>Faster Adoption
    Team proves delivery in shorter cycles, then evolve to longer cycles
    Key point: Consider shorter cycles/iterations
    SOURCE: Agile Unplugged/Creoss Business Solutions
  • 19. 10
    Challenge: Rigor
    • Adaptation, not “Casual-agile”
    • 20. Rigor, not “Story-bleeding”
    • 21. Accountability, not “Procrastination”
    • 22. Estimations based on historical truth, not “Thumb-in-the-air”
    • 23. Key point: rigor is being left behind due to casual-agile
  • 11
    Technique: Rigor
    • Rigor around
    • 24. Buyer/seller of artifacts
    • 25. Change control
    • 26. Velocity metrics
    • 27. Cycle/iteration transition
    • 28. Software factory metaphor (stacked working pattern)
    • 29. Meeting management
    • 30. Key point: inject a special “flavor” of rigor with the above concepts
  • 12
    Challenge: Integrating Agile
    • “My ecosystem has many existing projects flowing through it in its current form. How do I integrate an Agile initiative into what exists today?”
    • 31. “Can/Should we start with a pilot or should we convert completely, everything at the same time?”
    • 32. Is top down or bottom up more effective?
    • 33. Key point: how to integrate an Agile initiative into your shop?
  • 13
    Technique: Integrating Agile
    Solidify stakeholder support
    Select pilot project
    Select pilot project team
    Setup Agile support tools
    Solidify roles/routines
    Conduct pilot team training
    Execute Agile
    • Weekly heartbeat
    • 34. Artifact Review
    • 35. Cycle/iteration planning
    • 36. Cycle/iteration transition/retrospectives
    • 37. Snapshot metrics
    • 38. Change control
    • 39. Stand-ups
    • 40. Make Transparent, Inspect and Adapt
    Key point: apply a top-down support with bottom-up implementation your Agile adoption play
  • 41. 14
    Challenge: Velocity
    • Velocity==>Rate at which teams consistently deliver value
    • 42. Velocity==>Indicator of capacity / capability
    • 43. Best indicator for velocity is historical
    • 44. “Accuracy of velocity and speed of achieving this accuracy is directly proportionate to the frequency at which velocity metric is taken”
    • 45. More frequent snapshots, more accurate estimates
    • 46. Non-existent velocity==>poor estimates==>missed milestones
    • 47. Key point: do you truly understand what your team(s) are capable of producing (in terms of completed/working feature/functionality)?
  • 15
    Technique: Velocity
    • Re-factor velocity numbers at end of cycle/iteration
    • 48. Move to shorter cycles/iterations (weekly)
    • 49. Thurs-Wednesday
    • 50. Establish user story/use case metric at begining of effort
    • 51. Rigorous attention towards measuring true velocity
    • 52. Key point: leverage cycles/iteration transitions to solidify understanding of true-velocity
  • 16
    Challenge: Sustainability
    • “It is one thing to introduce Agile into your shop; it is yet another to sustain Agile over the long run”
    • 53. Most Agile adoption plays ==>Introduction of Agile
    • 54. Sustaining an Agile adoption initiative requires rigor==>adaptation with boundaries
    • 55. Key point: sustainability of Agile adoption requires rigor
  • 17
    Technique: Sustainability
    Scrum types (A, B,C)
    • Software Factory metaphor
    • 56. Rigor around Retrospectives
    • 57. Rigor around Metrics
    • 58. Consider dual-spin (advanced/enhanced Scrum)
    • 59. Key point: Continuous flow of cycles/iterations, disallow breakages in flow
    http://www.crisp.se/scrum/books/ScrumPapers20070424.pdf
  • 60. 18
    THE RECIPE!
    Summary
  • 19
    Summary
    Setting the stage
    We discussed the background/context from which the list of challenges and techniques originated from (pure experience!)
    Challenge / Technique
    We enumerated and discussed the Top 10 list of challenges and techniques that you can use in your shop today
    Recipe (combining techniques)
    We compiled all the techniques into one list
  • 67. 20
    Next steps
    Ask us about our Agile Adoption Assessment
    Development practices and tools
  • 68. 21
    Teaming
    Here is how we are partnered
    CREOSS Business Solutions - Agile Adoption expertise
    Visit us at www.creoss.com
    Visit our blog at www.agileunplugged.com
    ADC - MKS solutions for CA 2E and CA Plex
    Visit us at www.adcaustin.com