Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
11. Individuals and Interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
12. BE AGILE
-Team and collaboration
- Incremental
- Iterative
-Value driven
- Frequent delivery
- Product quality
- Inspect and adapt
- Self-organisation
35. - Prioritised set of estimated items
- Constantly in change as the situation changes
- Contains stories, bugs, refactorings, …
- Detailed appropriately
- Source of work for the Development team
PRODUCT BACKLOG
37. TASK
Each user story can be separated
into (technical) tasks.
As a plan to accomplish the work.
AS A …
I WANTTO …
SOTHAT …
Set up the database
Create API call
…
46. Be adaptive! Iterate!
Sprint
Fixed timebox in which the Scrum team
delivers a product increment
according to the Definition of Done.
between 1 and 4 weeks
47. SPRINT
Project progresses in sprints
Sprint commitment by Development team
No new requirements during the spint
Scrum team delivers a product increment
48. How do we plan?
Sprint Planning
Timeboxed meeting for the Scrum Team,
to pull work into the Sprint Backlog
max 2 hours per week of sprint
51. RELATIVE ESTIMATES
- Story points are more then just time
- Compare to reference item
- Faster, more accurate planning
- Independent of developer skills
Fibonacci: 1 2 3 5 8 13 ..
52. PLANNING POKER
1 - Product Owner explains item
2 - Developer compares with a reference item
3 - All cards are shown together
4 - Highest and lowest explained
5 -Team gets to a consensus, possible other round
53. Track progress during the sprint?
Daily Scrum
Timeboxed meeting for the Development team
to make sure the sprint goal is reached.
max 15 minutes
54. What did you do yesterday?
What will you be doing today?
Are there any blocking issues?
Everyone. Short.Turn by turn.
And take necessary steps after the Daily Scrum
56. What did we do good in last sprint?
What did we do less in the last sprint?
Are there any questions or uncertainties?
Are there any open items from last retrospective?
Everyone.Write down.
Group the items and discuss. Plan and take action.
58. Updated backlog!
Product Backlog Refinement
Scrum team keeps the product backlog up to date,
to have a shared understanding of what needs to be done
ongoing activity