Agile Project Management - Course Details

Agile Project Management

1. Agile Project Management

2. Introduction Today, project leaders and teams find themselves in an environment disrupted by exponential advances in technology and demands from customers for more immediate delivery of value. Agile techniques and approaches effectively manage disruptive technologies. In order to stay competitive and relevant, organizations can no longer be internally focused but rather need to focus outwardly to the customer experience. This speed of change will continue to drive large organizations to adopt an agile mindset in order to stay competitive and keep their existing market share.

3. 5 Success Stories That Will Make You Believe in Scaled Agile › ObjectStyle.Com

4. We are uncovering better ways of developing software by doing it and helping others do it. The Agile Manifesto Individual and Interactions Working Software Customer Collaboration Responding to Change Over Processed and Tools Over Comprehensive Documentation Over Contract Negotiation Over Following a Plan

5. Agile VS Traditional The Agile Manifesto Agile Customer Collaboration Responding to Change Working Solutions Highest Business Value in The Shortest Time Traditional Contract Negotiation Following A Plan Documentation Deferred Business Value Via Longer Delivery Time VS AGILE MYTHOLOGY Agile is an iterative method of managing product development projects in a highly flexible and interactive manner. The overarching focus of agile development is frequent delivery of high-quality, working, software. Agile ensures optimal business value is delivered through ongoing alignment between technology and the business.

6. 12 Principles Behind the Agile Manifesto The Agile Manifesto - 12 Principles Satisfy The Customer Welcome Changing Requirements Deliver Working Software Frequently Collaborate Daily Motivated Individuals Face-to-face Conversation Measure Of Progress Through Working Product Promote Sustainable Development Continuous Attention To Technical Excellence Simplicity Is Essential Self-organizing Teams Regularity Reflect On Continuously Improving

7. Agile vs. Waterfall

8. Enter your subhead line here Waterfall VS. Agile Agile Projects Traditional Projects (Waterfall) Fixed Estimated PLAN DRIVEN Scope Costs Time Part of Contract Flexible VALUE DRIVEN Scope Costs Time The plan create cost/ Schedule estimates Software release themes and features determine the time and cost estimate

9. A B C D Features Planned Features Developed A B C D Enter your subhead line here Waterfall VS. Agile BUDGET TIME Waterfall Development of the software flow sequentially from start point to the end point. Strategy & Recommendations AI / Wire Fire Visual Design & Copy Development & Coding Testing & Validation Deployment

10. Enter your subhead line here Waterfall VS. Agile BUDGET TIME Agile Agile method proposes and increment and iterative approach to software design. Features Developed Features Planned A B C D Strategy & Recommendations AI / Wire Fire Visual Design & Copy Development & Coding Testing & Validation Deployment Handoff to Dev A B C D Features Developed Features Planned Strategy & Recommendations AI / Wire Fire Visual Design & Copy Development & Coding Testing & Validation Deployment Handoff to Dev A B C D 4 Weeks 4 Weeks

11. Success Rate / Benefits Why Organizations Implement Agile Accelerate Product Delivery 62% Enhance Ability to Manage change priorities 56% Increase Productivity 55% Improve Software Quality 47% Enhance Delivery Predictability 44% Improve Business and IT alignment 44%

12. When it comes to measuring agile success, organizations report using these top metrics How Organizations Measure Agile Success 58% On-Time Delivery 48% Product Quality 46% Customer Satisfaction 46% Business Value 36% Product Scope

13. Keys to Success / Barriers against Agile Keys to Success / Barriers against Agile Consistent Practices & Process A Common Tools Across All Teams Agile Consultants Or Trainers Executive Sponsorship Internal Agile Supportive Team Company Culture Lack Of Experience Insufficient Management Support Inconsistent Practice And Process Resistance To Change BARRIERS AGAINST AGILE ADOPTION KEYS TO SUCCESS

14. Top Agile Management Tools Top Agile Management Tools Microsoft Excel Microsoft Project Atlassian / JIRA VersionOne Microsoft Team Foundation Server Google Docs HP Quality Center 68% 46% 45% 33% 24% 24% 23%

15. Agile Product Backlog Template Agile Product Backlog Template Priority Task Name Story Sprint Ready Status Story Points Assigned to Sprint High Sprint 1 No No In Progress 24 No Medium Task 1 Yes Yes Complete 8 Yes Medium Task 2 Yes Yes Complete 16 Yes Medium Task 3 Yes Yes Complete Yes Medium Sprint 2 Yes Yes In Progress 96 Yes Low Task 4 Yes Yes Complete 32 Yes Low Task 5 Yes Yes Complete 48 Yes Medium Task 6 No No Not Started 16 No Medium Sprint 3 Yes No In Progress 32 No Low Task 7 Yes No In Progress 8 No Medium Task 8 No Yes In Progress 8 No Medium Task 9 Yes No In Progress 16 No Medium Sprint 4 Yes Yes In Progress 64 Yes Low Task 10 Yes No In Progress 32 No Low Task 11 Yes Yes Complete 32 Yes Medium Task 12 Yes Yes Complete Yes Low Sprint 5 No No Not Started 64 No Low Task 13 No No Not Started 48 No Low Task 14 No No Not Started 8 No

16. Agile Sprint Backlog Template Agile Sprint Backlog Template Priority Backlog Item Story Points Responsible Status Original Estimate Day 1 Day 2 Day 3 Day 4 Day 5 Sprint Review User Story #1 8                   Task       7 5 3 Task       3 1 1 5 1 Task       1 0.5 3 User Story #2 1                   Task       3 3 0.5 0.5 2 Task       3 5 5 1 1 1 Task       2 2 5 1 1 User Story #3 5                   Task       8 6 Task       3 1 3 3 3 Task       1.5 1 0.5 0.5 1 1 Task       2 0.5 3 User Story #4 8                   Task       9 4 2 2 1 1 Task       6 6 3 3 3 1 1 Task       6 2 8 8 1 1 User Story #5 3                   Task       2 1 1 1 0.5 1 1 Task       6 6 6 0.5 3 9 Task       0.5 0.5 0.5 1 0.5 1 Total       78 60 59 41 20 18 14

17. Agile Project Charter Template Agile Project Charter Template Project Details Mission   Vision   Scope   Success Metrics   Date: Date: General Project Information Project Name   Project Champion   Project Sponsor   Project Manager   Stakeholders   Expected Start Date   Expected Completion Date  

18. Agile Test Plan Template Agile Test Plan Template Test # Date Action Expected Results Actual Results Pass? Tested By Tester Comment 1 6-Mar Logging in Should get to home screen User directed to different page   JKM Comment by Tester.. 2 12-Mar Signing up for webinar Get confirmation email Confirmation email received 3 20-Mar Click magnifying glass Whole page gets bigger Text changes sizes   4 1-Apr Click blog post hero image Go to blog post Go to blog post                                                                                                 Project Name --- Browser: --- Test Case ID --- Version: --- Written By: --- Description: --- Tested By: --- Tested On: ---

19. Agile User Story Template Agile User Story Template Priority User Story ID As a <type of user> I want to <perform some task> so that I can <achieve some goal> Final Story? H 1 Project manager View a status report from each team member Ensure the project stays on track. L 2 Employee Be reminded of upcoming deadlines Complete my tasks on time. M 3 Director See the big picture view of department work Stay in the loop.                                                                                        

20. Agile Methodologies Used Agile Methodologies Used What is Scrum? Scrum is a lightweight management framework with broad applicability for managing iterative and incremental projects of all types. In the Scrum, work is confined to a regular, repeatable one-week to one-month work cycle, known as Sprint What is KANBAN? KANBAN is a pull-based planning and execution method in which the team signals when they are ready for more work and pulls it into their queue. Teams track their work with cards that are kept on a KANBAN board. What is XP? Extreme programming known as XP is software development methodology intended to improve software quality and responsiveness to changing customer requirements. 58% SCRUM 10% Scrum / XP HYBIRD 8% Custom 7% SCRUMBAN 5% KANBAN 2% LEAN <1% XP

21. Characteristics of Four Categories of Life Cycles

22. An adaptive life cycle is a change-driven. It is an Agile way of doing things as it is intended to high level of changes. It needs on-going stakeholder’s involvement. Here iterations are very rapid usually with duration of 2 to 4 weeks and are fixed in time and cost. Agile Life Cycle

23. Like, a yearlong project will have multiple 2-4 week iteration and each iteration will execute Planning, Analysis, Design, Code, testing phases and deliver the result at the end of the iteration. Agile Life Cycle

24. Retrospectives At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The retrospective is about looking at the qualitative (people's feelings) and quantitative (measurements) data, then using that data to find root causes, designing countermeasures, and developing action plans

25. Daily Standups In many sports like (American) football and rugby, the team huddles before each play. The huddle is strategic: it keeps the team informed, connected, and calibrated throughout the game. For software teams, the stand-up is like the team’s huddle. It’s even commonly known as the daily scrum, and reinforces “we” to keep everyone aware of the team’s landscape and progress.

26. Demonstrations/Reviews As the team completes the features usually in the form of user stories, the team periodically demonstrates the working product. The product owner sees the demonstration and accepts or declines stories. In iteration-based agile, the team demonstrates all completed work items at the end of the iteration. demonstrate whatever the team has as a working product at least once every 2 weeks. That frequency is enough for most teams, so team members can get feedback that prevents them from heading in a wrong direction.

27. The Agile Process The Agile Process Increment #1 Features List #1 Increment #2 User Feedback + Features List #2 User Feedback + Features List #3 RELEASE AGILE PROJECT MANAGEMENT Product Vision Project Definition Initial Release Plan Contractual Agreement

28. The Agile Process The Agile Process Stockholders AGILE PROJECT MANAGEMENT Product Backlog Management Release Planning Release Backlog Management Product Owner Release 1.0 Release 1.5 Release 2.0 Gather and Filter Market Requirements From Stakeholders / Create Stories Development Request