Maximize Benefits of Agile Practices

Transcription

1 Maximize Benefits of Agile Practices January 2016 Author: Dr. Tonya M. Peterson, PMP, CSM

2 2 Agile Manifesto

3 3 A good entrepreneur has a very clear grasp of what the goal is, an unwavering sense of the goal, an utterly agile approach of getting there. John Katzman

4 Stakeholders Customer Satisfaction 4 Project Team Project Oversight How Can Agile Methodology Help?

5 5 Customer Satisfaction Users, clients, or end customers who are internal or external to the organization

6 6 Address User Needs Defining product features User Stories with Acceptance Criteria Gaining user feedback Sprint Review Meetings Delivering product value Deploy incremental functionality features Engaging users throughout project life Product Owner is an expert on product requirements and customer needs

7 Scrum Overview 7

8 8 Reduce Defects Working version of software through each sprint Test driven development approach Stories are considered complete when zero defects is achieved Automating test scripts increasing team productivity Develop during the day and test at night Testing is integrated with product inspection Product owner able to suggest adjustments Project team has insight into quality issues

9 Agile Development Agile Development Requirements Design Construct Test Project Duration 9

10 10 Introduce Change Refine the Product Backlog each Sprint Include new or changed backlog items into next sprint Change is expected Requirements emerge and evolve throughout the project Incorporate feedback from demos and usability testing Identify expectation mismatches early

11 Levels of Agile Scope 11

12 12 Improve Quality Breaking down scope into small units of work Focus on quality and collaboration Embracing technological excellence Strong design along with maintainable code Defining and elaborating requirements just in time Product features are current and relevant Incorporating continuous integration and testing Address issues immediately Completing work using the definition of done Develop, test, integrate, and document

13 13 Project Oversight Scrum Master, Project Manager, Project Sponsor, or executive management

14 14 Business Value Focus Identifying priority features of the Product Owner Team understands value-driven features Building the right product Requirements emerge and evolve along with change through appropriate trade-offs Product is what is expected and needed

15 15 Agile Scope Prioritization Investments Benefits Needs Satisfiers

16 16 Cost Control Fixed timescales and fixed budget Scope and product features are variable Compared cost of future development with value of future development Helps to identify end of a project Identified cost of each sprint based on consistent sprint lengths

17 Triple Constraints: Paradigm Shift 17 Fixed Scope Waterfall Time Cost Flexible

18 18 Relevant Metrics Accuracy built into project estimates Timelines and budgets are based on team actual performance and capabilities Development team defines estimated effort for project requirements Use of relative estimates based on team's knowledge and capabilities Refine estimated effort, time, and cost as the team learns more about the project Maintain sprint burndown chart based on team performance

19 19 Agile Metrics Velocity Burn down Charts

20 20 Achieve ROI Product development begins early in project Quicker speed to market with limited features Benefits / ROI can be realized as the product development continues Develop fully functional feature within each sprint Add new features in each sprint until fully functional version is available

21 Scope Horizontal & Vertical Slices 21 What to build: Slices of Scope How to build: Layers of Development Refer to:

22 22 Project Team Scrum Master, Developers, Business Analyst, Quality Assurance / Tester, Technical Writer, and UIX Designer

23 23 High Team Morale Agile: Discuss status and progress around taskboard Discuss requirements in workshops Discuss what s right for the product and project Team empowered to make decisions Team is highly cooperative Team has active involvement, cooperation, and collaboration Waterfall: Lengthy status reports Extensive specs Detailed project plans Approval required from change management committees

24 24 Team Development Stage Theme Team Behavior 1. Forming Getting Acquainted, Goal Setting, Organizing 2. Storming Active Listening, Assertiveness, Conflict Management 3. Norming Communication, Feedback, Affirmation 4. Performing Decision Making, Problem Solving, Rewarding Value Certification, Visioning, Communication Flexibility, Creativity, Thinking Playfulness, Humor, Networking, Entrepreneurial Thinking Multicultural Awareness, Mentoring, Future Driven 5. Adjourning Evaluating, Reviewing Celebrating, Brining Closure Adapted from Team Development Summary Sheet. Refer to

25 25 Improved Team Performance Customized team structures Limited size of five to nine team members Projects are able to have multiple scrum teams Improved team visibility Project team members know the project status and progress through daily scrum and spring review meetings Sprint retrospectives offer insight into continuous team improvement Introduction of a self-managing team allows for creativity Scrum master removes impediments and reduces interference Cross-functional teams allows for shared skills and growth

26 26 Retrospectives Valuable tool offering ability to adapt learnings going forward Safe environment to share What worked well? What did not work well? What should we do different? What should be continue to do?

27 27 Stakeholders All who have an interest in the project, from management and Product Owner to the Project Team and the customer or end user

28 28 Project Simplicity Value driven efforts No useless meetings No irrelevant documentation or artifacts Increased productivity for all stakeholders Continuous engagement throughout the project life Timely communication to all stakeholders Preserves interest of all stakeholders rather than catering to individual stakeholder interests

29 29 Collaboration Increased collaboration Project Team, Product Owner, and Scrum Master work closely on a daily basis Clear understanding of product vision Increased stakeholder engagement Direction through face to face discussions Influences positive and enduring working relationships Stakeholders share a sense of product ownership

30 30 Agile Methodologies: Additional Improvements Alignment with Business Partner Team Morale

31 31 Transparency Introduced feature prioritization to stakeholders Visibility to progress Increased stakeholder s trust Visibility to project progress and expectations Delivered working software early and frequent Early access to product during the project life

32 32 Agile Demos Demonstrate working product functionality Not a slide presentation Gain alignment / direction on product functionality Input into Product Backlog for future release / sprint planning sessions

33 33 Risk Reduction Introduced project investment in short durations / sprints Opportunity to fail fast Define a viable project approach Completed requirements each through a definition of done Usable features each sprint Introduced alterations to project processes and product direction Constant and regular feedback Reduced market risk Beta version released to potential market for a product review and insight Ability to make a material difference to the product outcome

34 Life of a User Story to a Card Wall 34

35 35 Going Forward Areas to be aware of when applying Agile practices

36 36 Agile Awareness Overall less predictability Software development is difficult Greater commitment and effort is required from everyone involved

37 Agile Team Skills 37 Visionary Problem Solver Product Knowledge Supportive Supportive Deals with Ambiguity Whatever It takes Applies WIT Attitude Adaptable to Change Strong Leadership Able to Multi-task Forward Thinking Effective Communicator

38 38 References EPMLive. (2014). 5 Benefits of Agile. Retrieved from: Layton, M. C. (2016). 10 Benefits of Agile project management. Retrieved from: Segue Technologies. (2015). 8 Benefits of Agile software development. Retrieved from: Waters, K. (2007). 10 Good reasons to do Agile development. Retrieved from:

39 39 Questions?