agile scrum: learn agile development for project managers
TRANSCRIPT
Learn Agile SCRUM Development for Project Managers …
Use the Agile approach to maintain focus on the rapid business
value delivery.
A working model using mission-driven measures in a team approach enables focus on effective solutions
Course Goals • Develop Scope/Value for Accelerated Deliverables • Learn Focus Points of Agile Scrum • Comparison with RUP, SDLC, Agile Scrum • Determine Product Backlog Stories & Grooming • Learn Standups, Other Meeting, and Retrospective • Document and Manage Stakeholders and Requirements • Capture & Clarify Constraints to Delivery of Solutions • Develop Metrics for Velocity & End-User Acceptance • Enable Collaboration of Stakeholders
Target Audience Who should take this course? • Subject Matter Experts (SMEs) • Product Owners and Sponsors • Business Process Managers • Business Process Users • Product, Project, and Program Managers • Business Analysts & Architects • Quality Assurance • System & Software Developers
Course Prerequisites • Some technical experience • Ability to collaborate and listen • Capability to capture and define business and
technical requirements • Interest in business analysis and information
architecture • Ability to collect and organize tasks, activities and
resources into diagrams and graphical models
Agile SCRUM Development for Project Managers …
Why Is Agile Scrum Needed? Section 1 Goal …
Understand why Agile Scrum methodology and methods are used.
Welcome • … to my Udemy Training course
• Hello, I'm Chuck Morrison
• My specialties are: Business Process Engineering, Software Systems Development, Cross-Functional Program and Change Management.
• My significant skills and accomplishments include ...
• My significant accomplishments also include ...
Agile Development – Accelerated Delivery
• Agile methods are based on real-life project experience of software professionals.
• Agile development offers a lightweight framework for supporting teams given constantly evolving functional and technical landscape.
• Agile development accelerates delivery of required business value.
• Company’s Business Systems Delivery
• Team Support Product & Services for Customers
• Undocumented Processes & Procedure
• What to Do … Next Steps …
Imagine …
Related Quotes • Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop
questioning. – Albert Einstein
• Continuous improvement is not about the things you do well — that’s work. Continuous improvement is about removing the things that get in the way of your work. The headaches, the things that slow you down, that’s what continuous improvement is all about. ~Bruce Hamilton
• Perfection is not attainable, but if we chase perfection we can catch excellence. -Vince Lombardi
• The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency. ~Bill Gates
• What gets measured, gets managed. ~Peter Drucker
Why Is Agile Scrum Needed? • Agile means being able to quickly change direction. • Time and money are not wasted building products & services no one
wants or won’t pay for. • Creation of product and services with minimum set of features
providing required value to clients • Scrum processes are clear about producing visible value as working
software on a regular basis. • Iterative incremental product and service delivery (sprints) maximizes
opportunity for frequent client feedback and ROI.
What’s This Course About? • Agile development offers a lightweight framework for
supporting teams
• The Agile approach maintains focus on the rapid business value delivery
• Collaborative development viable solution based on Agile Methodology and Methods
What you get from this course? • Discover and Develop Project Deliverables • Learn Agile Manifesto & Scrum Focus Points • Learn SWOT among RUP, SDLC, Agile Scrum • Learn Backlog Grooming and Sprint Story Iterations • Document Business Requirements and Stakeholders • Capture/Clarify Constraints/Mandates for Solutions • Develop Metrics for End-User Acceptance • Enable Collaboration Sponsors, Stakeholders, Users
What are course requirements? • Some technical experience desired. • Ability to collaborate and listen for business wants and
needs • Capability to capture and define business and technical
requirements • Interest in the fields of business analysis and information
architecture • Ability to collect and organize tasks, activities and resources
into diagrams and graphical models
Target Audience Who should take this course? • Subject Matter Experts (SMEs) • Product Owners and Sponsors • Business Process Managers • Business Process Users • Product, Project, and Program Managers • Business Analysts & Architects • Quality Assurance • System & Software Developers
Reducing Chaos Using Agile Scrum Methodology
Reducing Chaos Using Agile Scrum Methodology Section 2 Goal …
Capture information to determine what's known about and related to the problem(s) and issue(s) step by step.
What’s Agile Scrum Methodology? Agile Scrum Development – Accelerated Delivery as shown in the following diagram: • Adaptability, Risk, Business Value, Visibility • Strategy – Vision, Goals, Charter, Funding • Release – Backlog, Release Plan, Estimation • Iteration – Iteration Plan, Review, Retrospective • Daily – Standup, Acceptance • Continuous – Test Driven Development, Refactoring, Build,
Collaboration, Integration • Values – Adaptability, Transparency, Simplicity, Unity
Agile Manifesto The Agile Manifesto focuses on: • Individuals and interactions over
processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
What’s Accelerated Delivery?
Twelve Principles
q Customer Satisfaction q Welcome Changing Requirements q Working Software – Delivery q Substantial Development q Close, Daily Collaboration q Face-to-Face Conversation q Projects – Trusted Individuals q Technical Excellence q Simplicity q Regular Adaptation
What’s Accelerated Delivery?
Agile Iterative/Incremental Development
What Are Scrum Sprints?
What Are the Core Roles for Agile Scrum?
• Product Owner
• Development Team
• Scrum Master
What are Agile Scrum Ancillary Roles?
• Stakeholders
• Managers
The Scrum Task Board
Scrum (Daily Standup) • Each Day of the Sprint Development Team Meets • During Each Meeting, Team Members Answer:
– What did you achieve yesterday? – What do you plan to do today? – Will you encounter any impediments or roadblocks?
• Scrum Master Documents Identified: Impediments, Questions, & Issues
• Resolution/Details NOT Discussed in Meeting
Backlog Grooming (Story-Time) • Perform Product Backlog grooming:
• Process to estimate existing backlog effort or story points • Refining acceptance criteria for each story • Breaking larger stories into smaller stories
• Commonly Used Estimation Method Is Planning Poker • Meeting duration no longer than an hour • Meetings don't include breaking stories into tasks • Team decides number of meetings needed each week.
Agile Planning, Demo, and Closure Meetings
Section 3 – Agile Planning, Demo, and Closure Meetings
Scrum of Scrums (Dependencies)
• Each team designates a member to attend • Agenda Same as Daily Standup:
• What's your team achieved since the last meeting? • What will your team achieve before the next meeting? • What obstacles slow your team's progress or otherwise
present obstacles to your team’s progress? • Are you aware of dependencies your team may place in
another team’s path as obstacles?
Sprint Planning Meeting • Select Work to Perform • Sprint Backlog Detailing Performed • Communicate Sprint Volume/Velocity of Work • 8 Hour Time Limit
– Hours 1-4 Prioritize Backlog – Entire Team – Hours 5-8 Develop Sprint Plan – Development Team
• Follow-up with: Sprint Review & Sprint Retrospective
Sprint Review Meeting (Demo) • 4 hour time limit
• Review work Completed and NOT Completed
• Present Completed to Stakeholders “Demo”)
• Work not completed can't be demonstrated
Conclusion …
Section 4 – Conclusion …
Agile KPIs Agile KPIs • Team Enthusiasm • Team Velocity • Quality Delivered to Customers • Communication • Actual Stories Completed vs. Committed Stories • Technical Debt Management • Retrospective Process Improvement • Team’s Adherence to Scrum Rules and Engineering Practices • Team’s Understanding of Sprint Scope and Goal
Conclusion You’ve Completed the Course Goals … • Develop Scope/Value for Accelerated Deliverables • Learn Focus Points of Agile Scrum • Comparison with RUP, SDLC, Agile Scrum • Determine Product Backlog Stories & Grooming • Learn Standups, Other Meeting, and Retrospective • Document and Manage Stakeholders and Requirements • Capture & Clarify Constraints to Delivery of Solutions • Develop Metrics for Velocity & End-User Acceptance • Enable Collaboration of Stakeholders
Glossary For definitions of terms used in this course, please see
downloadable Glossary below …
For Further Reading … OO UML developed by “The 3 Amigos” Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software during 1994–95 with further development led by them through 1996 … Rational Software transferred to IBM … OO UML accepted by OMG & ISO Please see other References (attached) ...