Your SlideShare is downloading. ×

Agility Assessment - Roadmap to Making Your Business Users Happy


Published on

Published in: Technology, Business

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Agility Assessment21-May-2013Roadmap to Making Your Business Users Happy
  • 2. 2© Alliance Global Services 2013About AllianceAlliance is a software development and testing firm that partners with software,technology and information-intensive businesses on their mission critical work.Leveraging agile practices, Alliance architects and builds software applications,platforms and products that become primary drivers of innovation and revenuegrowth for its clients and their businesses. Alliance is recognized for driving qualityand speed-to-market when business success depends on the software inside.Founded in 1994, Alliance is headquartered in suburban Philadelphia inConshohocken, PA.Today’s SpeakersLauren Feehrer Ralph Decker
  • 3. 3© Alliance Global Services 2013AgendaWhy Agility? What does it take?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 4. 4© Alliance Global Services 2013Why Agility?Key point is to first understand – why are trying to be Agile? What benefit(s) areyou looking for?From: 7th Annual State of Agile Development Survey 2012
  • 5. 5© Alliance Global Services 2013Challenges / BenefitsSource: VersionOne’s “Five Myths of Agile Development” Whitepaper
  • 6. 6© Alliance Global Services 2013Why Agile?“In the long run, the only sustainable source ofcompetitive advantage is your organization’s ability tolearn faster than your competition.”- Peter Senge, MIT
  • 7. 7© Alliance Global Services 2013Agility Impacts Entire Software EcosystemFrom: Forrester Research, Inc.
  • 8. 8© Alliance Global Services 2013AgendaWhy Agility?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 9. 9© Alliance Global Services 2013Trying to Optimize ThisValue(Releasable Product)Quality(Reliable, Adaptable Software)Constraints(Cost, Schedule, Scope)
  • 10. 10© Alliance Global Services 2013Focus on the Right Software FirstBuilt RightRight SoftwareUselessStuffWaste ofEffortMaintenanceNightmareSuccess
  • 11. 11© Alliance Global Services 2013Do you? Can you?• Have a common understanding amongstthe whole team?• Have a clear, shared language for domainconcepts?• Have a prioritized backlog of small,independent user stories?• Have acceptance criteria understood foreach user story?• Get rapid feedback from users andproduct owners?• Communicate a new user story in a fewsentences?• Have all your user stories understood bythe entire team?
  • 12. 12© Alliance Global Services 2013AgendaWhy Agility?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 13. 13© Alliance Global Services 2013The Case for Culture Shift to AgileI believe that the prevailing system of managementis, at its core, dedicated to mediocrity, if forcespeople to work harder and harder to compensatefor failing to tap the spirit and collectiveintelligence that characterizes working together atits best.”- Peter Senge, MIT“ ...of all the events that engage people at work,the single most important — by far — is simplymaking progress in meaningful work.”
  • 14. 14© Alliance Global Services 2013Culture & Teamwork• “Favor people over processes &tools”• “The TEAM commits to what can bedelivered”• “The TEAM inspects and looks forways to improve”Inability to changing Organization Culture was the #1reason cited for Agile project failures.From: 7th Annual State of Agile Development Survey 2012People:• Paradigm Shift: Project Manager to “Scrummaster”• Product Owners “in the game” from start to finish• Direct customer (end-user) engagement in full developmentprocess
  • 15. 15© Alliance Global Services 2013Do these people exist in your organization today?
  • 16. 16© Alliance Global Services 2013Can you? Do you?• Does the team work in specialized silos or as cross functionalgeneralists?• Is the entire team dedicated to the release?• Is the Product Owner part of the team?• Is everyone required to release software to customers on theteam?• Are commitments met?• Is the pace sustainable?• Do you get feedback for each iteration?
  • 17. 17© Alliance Global Services 2013The Essence of Agile CultureTeam members can be developers, testers, analysts,architects, writers, designers and even users. The team iscross-functional, which means that between all its membersthey possess sufficient skills to do the work. There is nodictated leadership hierarchy within the team members.
  • 18. 18© Alliance Global Services 2013AgendaWhy Agility?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 19. 19© Alliance Global Services 2013Technical Practices• Easiest way to go faster is to automate• And keep the code Clean• Easiest place to start … if Agile is a Technology lead initiative• Mandatory to be able to deliver short, rapid iterations of highquality software
  • 20. 20© Alliance Global Services 2013Can you? Do you?• Can any team member build and test the software with pass/failresult with a single click?• Or, do you have an automated CI tool to do that for you?• Does it take less than 10 minutes for the build process?• Do all developers follow version control best practices?• Do (nearly) all unit tests pass all the time?• Does the team self-police for code smells?• Does the team use code analysis tools?
  • 21. 21© Alliance Global Services 2013AgendaWhy Agility?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 22. 22© Alliance Global Services 2013Quality• Baked-In Quality• Not just bugs, include User Experience• Reducing QA cycle time imperative to short iterations andflexibility to make changes• Ensures each iteration is producing valuable, usable software
  • 23. 23© Alliance Global Services 2013Can you? Do you?• Automatically run acceptance test criteria against any build?• Test in parallel to iteration development?• Keep the automated test suite up-to-date?• Have fewer than 5 bugs per month in team’s finished product?• Fix bugs before adding new features?• Regularly deliver fully working, tested software?
  • 24. 24© Alliance Global Services 2013AgendaWhy Agility?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 25. 25© Alliance Global Services 2013Lean IT required• Developing & Testing faster is nice.• AND you need more than that to be successful long term• Project funding and prioritization• Dedicated team staffing• DevOps for release & run• Self-service cloud for dev/test environments
  • 26. 26© Alliance Global Services 2013Can you? Do you?• Prioritize & budget for projects on an ongoing basis?• Use a lightweight project management framework?• Provide the right dedicated staffing for a project to deliver?• Measure the quality and predictability of delivery?• Make tradeoffs to get business features out on time?• Invest in tooling to support Agile dev, test, and ops teams?• Create visibility of metrics and results?
  • 27. 27© Alliance Global Services 2013AgendaWhy Agility?Right SoftwareCulture & TeamworkTechnical PracticesQualityIT PracticesAssessment
  • 28. 28© Alliance Global Services 2013Assessment Tool3.00We have a common understanding amongst all team members as to the purpose ofthe software and the development project. We all know "Why" we are investing inthis, "Who" the users are, and "What" is important and can use that understanding toguide implementation choices and tradeoffs.3.00The Product Owner and other business sponsors and the technical team membersuse a common language with a well-understood vocabularly to describe the roles,actions, calculations, and entities involved or managed by the system.3.00We have a prioritized backlog of features and enhancements that is composed ofsmall, independent user stories (INVEST)3.00We regularly (at least once per iteration) review the backlog and ensure that eachstory has well defined acceptance criteria, is understood by the team, and meets our"Definition of Ready"3.00Our sprint planning sessions are efficient and effective, because the user stories arewell prepared, the team understands the stories quickly, and is able to providereasonable sizings quickly. We rarely have to extend the planning session past thetimebox.3.00Provide a rating for each question, with 1-Strongly disagree, 3-Neutral, and 5-Strongly AgreeRight SoftwareCommon UnderstandingShared LanguageProduct BacklogBacklog GroomingSprint Planning
  • 29. 29© Alliance Global Services 2013Results012345Right SoftwareTeam & CultureTechnical PracticesQualityLean IT
  • 30. 30© Alliance Global Services 2013To Recap• Define Agile Success• Assess your team & organization• Improve key areas• Continuous Improvement
  • 31. 31© Alliance Global Services 2013QUESTIONS AND ANSWERS
  • 32. 32© Alliance Global Services 2013Thank YouLauren FeehrerDirector of Customer Experiencelfeehrer@allianceglobalservices.comwww.allianceglobalservices.comRalph DeckerDirector - Solution