Let's learn it in a pragmatic way
Frontend Developer 👨💻
Productivity and efficiency addict 🤓
Human and animal interaction lover 🐶
Insatiable Traveler 🛫
Explain what is Agile.
The importance of being Agile.
Explain a way of working with Agile (Scrum).
Point out the pain points of the Scrum methodology.
How to facilitate an Agile environment.
In +50 slides
😈
iterations
rules
deliverings
👀 Visibility
😀 Client satisfaction
☯️ Transparency and honesty
👩👩👦👦 Team spirit environment
🔝 Productivity increase
🔄 Continuous improvement
👮 More autonomy and responsibility
💑 Emotional bonds
😑 A lot of meetings
❗ Not applicable to big hierarchies
🆘 Difficult to deal with external dependencies
⏳ No finite end
People to work
Things to do
A way to do things
1- SCRUM Team
SCRUM
1- SCRUM Team
SCRUM
Who decides what to do
Who develops features
Who assures Agile values
Multidisciplinar group of people who can develop, deliver and deploy to production all kind of User Stories
Decides which way should the product go. He prioritizes the Product Backlog and motivates the team
Ensures the team lives agile values and principles and follows the processes and practices the team agreed they would use
1- SCRUM Team
1- SCRUM Team
Multidisciplinar group of people who can develop, deliver and deploy to production all kind of User Stories
Decides which way should the product go. He prioritizes the Product Backlog and motivates the team
Ensures the team lives agile values and principles and follows the processes and practices the team agreed they would use
1- SCRUM Team
Multidisciplinar group of people who can develop, deliver and deploy to production all kind of User Stories
Decides which way should the product go. He prioritizes the Product Backlog and motivates the team
Ensures the team lives agile values and principles and follows the processes and practices the team agreed they would use
2- Product Backlog
👉 It never ends
👉 Gives value to the user
👉 Is prioritized by the Product Owner periodically
👉 The level of detail depends on the position of the task
👉 Is estimated, at least the top priorities
3- Agreements
✔️ Requirements for a task to be considered
✔️ Requirements for a task to be considered finished
✔️ When do the meetings
Bad practices:
The company decides when to do the meetings
There is no definition of ready or done
Product Owner
DEV Team
Scrum Master
🧐
👨💻
🤴
+
+
=
Creates & prioritizes
Develop
Promotes and assures
🗣️ Daily meetings
🏁 Sprint planning
📝 Backlog refinement
Meetings that have to be celebrated in order to do SCRUM.
🎉 Sprint review
🛡️ Retrospective
Know the status of the sprint and the team
Implementation details. Alert!!
Off-topic conversations
Technical conversations finding solutions
Reporting to the Product Owner
Cut things fast. Break wrong habits. Ask for focus
Have to talk something? Do it later.
Make a circle
Plan the work of the next sprint
👉 The Product Owner explains the goal of the sprint
👉 Ask as much as needed for knowing the requirements
👉 The DEV Team decides how much they can afford
👉 Think about details. How to implement?
👉 Detect possible blocks
👉 Detect third party dependencies
Setting unrealistic expectations
Don't have a prioritized backlog
The Product Owner decides how much work
Break tasks into smaller tasks. Dividi e vinci.
Check tasks complexity the spring before.
Ask for a constant Product Backlog prioritization
Update the Product Backlog
👉 The Product Owner and some of the DEV Team
👉 Add/Remove Stories
👉 Estimate tasks
👉 Update old tasks
Big estimations at the top of the Product Backlog
Tasks not estimated
Too much details for each estimation
Use timers for each task 5 min top. Sometimes, 3 min extra
Question Stick. Who has the stick has to ask. Then pass it.
Show the product increment and analize the next move
👉 Show the result of the sprint
👉 Explain the Goal and what has been achieved
👉 Impediments the team found
👉 In which direction should the product go
👉 Should we stop? Should we continue? METRICS!
Selfish Product Owner. He says: I did
Cheating. Showing development with bugs
The team doesn't explain challenges
It's called or treated as a DEMO
The PO is presenting all the results
Each team should present their User Stories.
Ask for challenges.
Use timers.
Team should only present working software
Analyze and improve as a team
👉 What went well
👉 What can be improved
👉 Actions for next sprint
Taking as personals some comments
Tell what happens in retrospectives to the outsiders
The actions have no owners:
Outsides/managers are coming
Not review past actions
Discussions dominated by one or two people
"improve communication"
"Refactor more"
Take it seriously. Be honest with your workmates.
Encourage people to participate, make everyone speak and give constructive feedback .
Materialize opinions with post-it. Each has 3 votes, do DOT VOTING
After, assign owners to the actions
Prioritizes
Develop
Assist to
Assist to
Assist to
Decided
Facilitates
Facilitates
Facilitates
Develops during
Create
Information about Scrum
Oficial documentation
🔗 https://www.scrumguides.org/docs/scrumguide/v1/scrum-guide-es.pdf