• Like
  • Save
Agile methodology   v 4.5 s
Upcoming SlideShare
Loading in...5
×
 

Agile methodology v 4.5 s

on

  • 2,638 views

 

Statistics

Views

Total Views
2,638
Views on SlideShare
2,638
Embed Views
0

Actions

Likes
1
Downloads
94
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Agile methodology   v 4.5 s Agile methodology v 4.5 s Presentation Transcript

    • Agile Methodology
      David Mann, CIO
      July 8, 2010
    • People are more important than any process!
      2
    • The most important thing about process is "To Have One"
      • Examples of SDLC processes:
      • Agile (MSF for Agile, SCRUM, LEAN, …)
      • Waterfall
      • Spiral
      • Extreme Programming
      • ASD
      • Rational Unified
      3
    • 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
    • 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
      • Waterfall is more suitable for static models with defined unchangeable scope. It is appropriate for maintaining mature systems with mature business model
      5
    • Agile Misconception
      • Agile is not about rushing things; but if Agile is applied things gets delivered faster with higher quality. Why?
      • Short Sprints (iterations) - 2 to 3 weeks
      • Full Customers Involvement to adjust course
      • Frequent Releases & Check-Points
      • Multi tracks
      • Focusing on delivering software (not process)
      • Agile does not mean chaos:
      • Think of Agile as many micro-waterfalls
      • Agile has “change control“ after each sprint (but less formal)
      • 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
    • 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
    • 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:
      • Changing scope & requirements to gain the highest ROI
      • Changing plan & processes to reduce cost
      • Changing solution for the best design & performance
      • Changing QA test for the ultimate quality
      • Changing the deployment for enhance SLA
      • Adjusting to the marketplace and competitors
      • Agile is about embracing change
      • Agile is about customer’s active participation and not the end-result victim
      8
      “The only constant in the universe is change”
    • 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
    • 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
    • Agile Development Methodology
      Correct the Course
    • Perceived Challenges with Agile:
      • Moving Deadlines
      • Over Budget
      • Difficult ROI Calculation
      12
    • 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:
      • 45% of features built are never used
      • 19% are rarely used
      • 16% are sometimes used
      • 13% are used often
      • 7% are always used
      • Over Budget: IT expenditure as a percentage of the revenue; set a budget for a project and develop within that budget
      • ROI Calculation: with shorter and frequent release cycle, ROI can be measured against actuals to make better decisions and reduce risk
      13
    • 14
      PMD - Business Analyst
      Responsibilities: DEFINE
      • Own the Product which means PMD is empowered to make Product decisions on behalf of the business
      • Buy vs. Build, Competitive Analysis, Customer Research, Product Strategies
      • Document Vision, High-Level Features, Persona, Market Opportunities, ROI (PDD)
      • Document Detail Requirements, Business Workflows Diagrams, Use Cases, Reports Mockup (BRD)
      • Legal and IP Opportunities
      • Prioritize Features with Business
      • Approve Solution & Prototypes with Business
      • Coordinate Users Involvement, UAT with business
      • Business Rollout Plan including Beta/Pilots
      • Users Training and Adoption
      • Manage Cultural Ramifications
      • Users Surveys, Feature and Usage Matrix and Reports, Product Roadmap
      QA Tester
      Responsibilities: TEST
      • Validate Solution which must meet or exceed requirements and quality
      • Create Test Plan and Provide Estimates
      • Test Cases including White-Box & Black-Box
      • Bug-Log and Reports
      • Test Automation
      • Regression, Integration and Smoke Tests
      Architect
      Responsibilities: DESIGN
      • Select Tools and Technologies, framework, coding standards, source control
      • Solution Design must meet business vision plus it needs to be easy, fast, and wow
      • Database Model and Data Dictionary
      • Design needs to include quality, security, availability, expandability, scalability, and maintainability
      • Write and Drive TDD
      • Prototypes
      • BI
      • Design Executive Dashboards and Reports
      PMO - Project Manager
      MSF for Agile Methodology
      Roles & Responsibilities
      Release Manager
      Responsibilities: RELEASE
      • Technical Rollout Plan
      • Production Requirements
      • Operational SLA and Guides
      Sponsor & Business Responsibilities: VISION
      • Communicate Vision
      • Provide Financials
      • Kickoff Meeting
      • Empower Leaders and Team Players
      • Support Established Processes
      • Approve Priorities, Deadlines, & Prototypes
      • UAT by Business
      • Celebration
      PMD
      Business
      Analyst
      Release
      Manager
      Sponsor
      &
      Business
      Architect
      QA
      Tester
      Developer
      Developer
      Responsibilities: BUILD
      • Write Program Code following best practices
      • Conduct Unit Testing
      • Document Work
      • Fix Bugs
      PMO - Project Manager
      Responsibilities: DELIVER
      • Manage Sponsor’s Expectations
      • Project Plans & Sprint Plans
      • Team Communication including Project Status, Meetings, Executive Reports
      • Project Budget Management
      • Resource Management
      • Obtain Estimates
      • Keep trends, Actual vs. Estimates
      • Work with Managers to Assign Tasks & Hold team members Accountable for the deliveries
      • Change Control
      • Risk Management; Lessons Learned
      • Coordinate Technical Rollout Plan and Business Rollout Plan
      • Portfolio Management
      • SDLC & Process Improvements
    • 15
      PMO - Project Manager
      MSF for Agile Methodology
      Foundational Principles - Team
      PMD
      Business
      Analyst
      • Foster open communications
      • Work toward a shared vision (focus on delivering business value)
      • Empower team members
      • Establish clear accountability
      • Deliver incremental value
      • Stay Agile & expect change
      • Invest in Quality
      • Learn from experiences
      • Partner with customers
      Release
      Manager
      Sponsor
      Business
      Architect
      QA
      Tester
      Developer
    • 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
    • Q & A