Agile and SCRUM Framework
- Advertisement -
In this article we will look at Agile SCRUM Framework and some facts of Agile SCRUM. SCRUM is most popular and extensively used flavor of Agile methodology.
Before i describing about the SCRUM framework we will see some facts about the Agile SCRUM which we will clear your picture about how Agile SCRUM framework works.
- Advertisement -
Facts about Agile and SCRUM
- Agile is a methodology, Scrum is the process
- Agile requires better & continuous planning
- Agile makes project execution dynamic & adaptive
- Agile requires better designs & documents
- Agile prefers completing features in one iteration
- Agile requires deliverables from each story
- Scrum iterations should ideally be of 2 weeks
- Scrum requires / enforces close working of teams
- Agile focuses on effectiveness over efficiency
- Iterations once planned should not be changed, preferably
Agile SCRUM Framework:
Roles and Responsibility in Scrum Framework:
Product Owners
- Envision the roadmap
- Define & refine the Backlog
- Prioritize & Revise on the basis of solid data
- Suggest, Negotiate & Accept deliverables
- Bear responsibility of delivering the product
Scrum Master – Serves, Leads & Facilitates
- Safeguard SCRUM process
- Remove obstacles
- Facilitate collaboration
- Acts as a sheepdog of the team
- Listening – Meant not spoken !
- Leading by serving
- Serving by leading
Delivery Teams
- Engineering (Dev. & QA)
- Tech Writers, Architects & Product Owner
- Business people & other experts
- What do they do ?
- Commit to sprints
- Estimate effort
- Plan their own work
- Use the Scrum Master to remove their obstacles
- Straight talk – Raise all concerns in the daily standup
- Question everything that is not understood
- Even if you are not accountable, you are responsible
Sprint Planning Meeting:
- Team determines actual velocity
- Review Sprint Backlogs
- Decompose features into tasks, using WBS
- Estimate for each task
- Typical task size is 0.5 – 2 days
- Team members signup for tasks, they are not assigned
- Consensus: Fist of five
- Feature is not done until it is fully tested & accepted by the Product owner
Daily Scrum Meeting:
- Rules:
- Standup – to ensure quick completion
- Daily 15 minutes
- Same time, same place everyday
- Only 3 topics per team member
- No problem solving, only reporting/escalation
- Stake holders can observe, not contribute
- Action the impediments, not the decisions
Sprint Demo & Review
- Informally present the outcome of the sprint to all stakeholders
- No MS-PowerPoint, only present deliverable ‘as is’ basis
- Discuss tasks completed, not time spent !
- Analyze missed & unplanned tasks
- Review burn-down chart
- ‘Demo’ all deliverables & assert doneness
- Review what was done & what was not !
- Summarize lessons learnt & action plan
5 Level of planning:
