Scrum Master Preparation
Artifact:
- Product Backlog
- Sprint Backlog
- Increment
Sprint Event:
- Sprint
- Sprint Planning
- Sprint Review
- Sprint Retrospective
- Daily Scrum
Accountability:
- Product Owner
- Developer(Dev,Test,Dev-ops)
- Scrum master
- Individuals and Interactions over Processes and Tools
- Working Software over Documentation
- Customer Collaboration over Contract negotiation
- Responding to Change Over Following a plan
Scrum
As a agile Framework
A Mechanism to Optimize the Value Delivery System
A Mechanism to guide Changes
-Effectiveness and Efficiency
Agility
Responding to Change
Rapid
Fast Delivery
Lean
Minimal Waste
Succeeding with Agile and Scrum requires being rapid and lean
Agile Mind Set
Setbacks as Learning Opportunities
Adapt Short Delivery Cycles, Collaboration and Change
Focus on Delivering Value
Agile Principles -12
Project
Early and Continuous delivery of Valuable Software
I Know it When i see it
You Ain’t Gonna Need it
Welcome Change Requirements
Even late in Development
Harness Change for the Customer’s Competitive advantage
Deliver Working Software frequently
Couple of week to couple of month
Shorter timescale
Sustainable Development
Developer, Sponsor and users -Maintain Constant Pace indefinitely
Working software is Primary measure of Progress
Product
- Simplicity Maximizing the amount of work not done is essential
- Continuous attention to technical excellence and good design enhances agility
People
Face to face conversion
Business people and developers must work together daily throughout the project
The best architectures, requirements and designs emerge from Self -Organizing Teams
Build Projects around motivated Individuals. Give them the environment and support they need and trust them to get the job done
Process
At Regular intervals, the team reflects on how to become more effective, then tunes and adjusts it behavior accordingly
No comments:
Post a Comment