Agile methodology v 4.5 s

  • 2,169 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,169
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
95
Comments
0
Likes
1

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. Agile Methodology
    David Mann, CIO
    July 8, 2010
  • 2. People are more important than any process!
    2
  • 3. The most important thing about process is "To Have One"
    • Examples of SDLC processes:
    • 4. Agile (MSF for Agile, SCRUM, LEAN, …)
    • 5. Waterfall
    • 6. Spiral
    • 7. Extreme Programming
    • 8. ASD
    • 9. Rational Unified
    3
  • 10. PMI PMBOK (PMP)
    CMM
    1969
    1991
    MSF 4.0
    2006
    MSF
    CMM
    1994
    1991
    Scrum
    DSDM
    Extreme Programming
    Feature Driven (FDD)
    Adaptive (ASD)
    Lean
    Crystal Clear
    MSF 4.0 for Agile
    1993
    1995
    1999
    2000
    2000
    2003
    2005
    2006
    Rational Unified Process
    1981
    MSF 4.0 for CMM
    2006
    Some processes are more Adaptive
    Some processes are more Predictive
    Adaptive/Predictive Scale
    ADAPTIVE
    PREDICTIVE
    AGILE
    ITERATIVE
    WATERFALL
  • 11. Which one is right for me?
    • Agile is more suitable for new product development where the scope gradually emerges and continues to evolve. It is appropriate for new business model in a changing marketplace
    • 12. Waterfall is more suitable for static models with defined unchangeable scope. It is appropriate for maintaining mature systems with mature business model
    5
  • 13. Agile Misconception
    • Agile is not about rushing things; but if Agile is applied things gets delivered faster with higher quality. Why?
    • 14. Short Sprints (iterations) - 2 to 3 weeks
    • 15. Full Customers Involvement to adjust course
    • 16. Frequent Releases & Check-Points
    • 17. Multi tracks
    • 18. Focusing on delivering software (not process)
    • 19. Agile does not mean chaos:
    • 20. Think of Agile as many micro-waterfalls
    • 21. Agile has “change control“ after each sprint (but less formal)
    • 22. Agile has meaningful short documents; prototypes clarify requirements and design; all team members work in a project-room to reduces documents and meetings; the team must focus on delivering quality software and not just documents
    6
  • 23. MSF for Agile Development
    Agile has tracks not phases; teams dash to the finish-line without waiting for each other
    Plan
    QA/Stabilize
    Envision
    Build
    Deploy
  • 24. What is Agile about?
    • Agile is about putting something in front of the business/customer quickly so that business and IT can adjust course by:
    • 25. Changing scope & requirements to gain the highest ROI
    • 26. Changing plan & processes to reduce cost
    • 27. Changing solution for the best design & performance
    • 28. Changing QA test for the ultimate quality
    • 29. Changing the deployment for enhance SLA
    • 30. Adjusting to the marketplace and competitors
    • 31. Agile is about embracing change
    • 32. Agile is about customer’s active participation and not the end-result victim
    8
    “The only constant in the universe is change”
  • 33. Waterfall Development Methodology
    Start
    Scope / Requirements
    Design
    Build / Coding
    Quality Assurance
    Deploy
    Target
    What if the Target is changed:
    Lost Time & Money!
    Waterfall has poor success rate in the industry
    New Target
  • 34. Agile Development Methodology
    Success !
    Start
    Sprint 1
    Sprint 2
    Sprint 3
    Sprint 4
    Sprint 5
    Sprint 6
    Sprint 9
    Sprint 8
    Sprint 7
    Target
    New Target
    New Target
  • 35. Agile Development Methodology
    Correct the Course
  • 36. Perceived Challenges with Agile:
    • Moving Deadlines
    • 37. Over Budget
    • 38. Difficult ROI Calculation
    12
  • 39. Solutions: Agile requires a mind-shift
    • Moving Deadlines: have a strict discipline on the feature list (features diet). Go to market with the minimum set of features and continue your growth (ex. Adobe Reader 9.3, iPhone 4.0, Flash Player 10.1). Standish study shows that:
    • 40. 45% of features built are never used
    • 41. 19% are rarely used
    • 42. 16% are sometimes used
    • 43. 13% are used often
    • 44. 7% are always used
    • 45. Over Budget: IT expenditure as a percentage of the revenue; set a budget for a project and develop within that budget
    • 46. ROI Calculation: with shorter and frequent release cycle, ROI can be measured against actuals to make better decisions and reduce risk
    13
  • 47. 14
    PMD - Business Analyst
    Responsibilities: DEFINE
    • Own the Product which means PMD is empowered to make Product decisions on behalf of the business
    • 48. Buy vs. Build, Competitive Analysis, Customer Research, Product Strategies
    • 49. Document Vision, High-Level Features, Persona, Market Opportunities, ROI (PDD)
    • 50. Document Detail Requirements, Business Workflows Diagrams, Use Cases, Reports Mockup (BRD)
    • 51. Legal and IP Opportunities
    • 52. Prioritize Features with Business
    • 53. Approve Solution & Prototypes with Business
    • 54. Coordinate Users Involvement, UAT with business
    • 55. Business Rollout Plan including Beta/Pilots
    • 56. Users Training and Adoption
    • 57. Manage Cultural Ramifications
    • 58. Users Surveys, Feature and Usage Matrix and Reports, Product Roadmap
    QA Tester
    Responsibilities: TEST
    • Validate Solution which must meet or exceed requirements and quality
    • 59. Create Test Plan and Provide Estimates
    • 60. Test Cases including White-Box & Black-Box
    • 61. Bug-Log and Reports
    • 62. Test Automation
    • 63. Regression, Integration and Smoke Tests
    Architect
    Responsibilities: DESIGN
    • Select Tools and Technologies, framework, coding standards, source control
    • 64. Solution Design must meet business vision plus it needs to be easy, fast, and wow
    • 65. Database Model and Data Dictionary
    • 66. Design needs to include quality, security, availability, expandability, scalability, and maintainability
    • 67. Write and Drive TDD
    • 68. Prototypes
    • 69. BI
    • 70. Design Executive Dashboards and Reports
    PMO - Project Manager
    MSF for Agile Methodology
    Roles & Responsibilities
    Release Manager
    Responsibilities: RELEASE
    • Technical Rollout Plan
    • 71. Production Requirements
    • 72. Operational SLA and Guides
    Sponsor & Business Responsibilities: VISION
    • Communicate Vision
    • 73. Provide Financials
    • 74. Kickoff Meeting
    • 75. Empower Leaders and Team Players
    • 76. Support Established Processes
    • 77. Approve Priorities, Deadlines, & Prototypes
    • 78. UAT by Business
    • 79. Celebration
    PMD
    Business
    Analyst
    Release
    Manager
    Sponsor
    &
    Business
    Architect
    QA
    Tester
    Developer
    Developer
    Responsibilities: BUILD
    • Write Program Code following best practices
    • 80. Conduct Unit Testing
    • 81. Document Work
    • 82. Fix Bugs
    PMO - Project Manager
    Responsibilities: DELIVER
    • Manage Sponsor’s Expectations
    • 83. Project Plans & Sprint Plans
    • 84. Team Communication including Project Status, Meetings, Executive Reports
    • 85. Project Budget Management
    • 86. Resource Management
    • 87. Obtain Estimates
    • 88. Keep trends, Actual vs. Estimates
    • 89. Work with Managers to Assign Tasks & Hold team members Accountable for the deliveries
    • 90. Change Control
    • 91. Risk Management; Lessons Learned
    • 92. Coordinate Technical Rollout Plan and Business Rollout Plan
    • 93. Portfolio Management
    • 94. SDLC & Process Improvements
  • 15
    PMO - Project Manager
    MSF for Agile Methodology
    Foundational Principles - Team
    PMD
    Business
    Analyst
    • Foster open communications
    • 95. Work toward a shared vision (focus on delivering business value)
    • 96. Empower team members
    • 97. Establish clear accountability
    • 98. Deliver incremental value
    • 99. Stay Agile & expect change
    • 100. Invest in Quality
    • 101. Learn from experiences
    • 102. Partner with customers
    Release
    Manager
    Sponsor
    Business
    Architect
    QA
    Tester
    Developer
  • 103. 16
    Production
    Release
    PDD
    Test
    Complete
    UAT
    Adoption
    BRD
    Rollout
    Plans
    Prototype
    TDD
    Test
    Plan
    Code
    Complete
    Agile Process & Deliverables
    Repeated for each Sprint
    Envision
    Deploy
    Stabilize (Testing)
    Plan/Design
    Build
  • 104. Q & A