Victor Ribero

The goal for today

In 66 slides

¿What is Agile?

Values

👫 Individuals and interactions over processes

👨‍💻 Working software over comprehensive documentation

🗣️ Customer collaboration over contract negotiation

🏃 Responding to change over following a plan

The best architectures, requirements, and designs emerge from self-organizing teams

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly

Prioritize

Pragmatic

Customer Centric

Empathic

Honest

Benefits

😀 Client satisfaction

👀 Visibility

👮 More autonomy and responsibility

👩‍👩‍👦‍👦 Team spirit environment

Benefits

🔝 Productivity increase

🔄 Continuous improvement

☯️ Transparency and honesty

💑 Emotional bonds

Disadvantages

😑 A lot of meetings

❗ Not applicable to big hierarchies

🆘 Difficult to deal with external dependencies

⏳ No finite end 

Kanban

👉 Usage of the Kanban board

👉 Tasks ordered by priority

Kanban

Kanban

Materialize task and its priority makes you more efficient .

It also clears your brain and let you focus on what's needed

Kanban

👉 Easy to see the priorities

👉 Easy to know the status of the tasks

👉 Visibility of the work to do

👉 Everyone knows the requirements of the states

Extreme Programming Values

👉 Simplicity - Do what has been asked to do. No more.

👉 Communication - Talk face to face

👉 Feedback - Talk about the project. Changes are welcome.

👉 Respect - Everyone give and receive the respect they deserve.

👉 Courage - Tell the truth always, you don't work alone

Extreme Programming Practices

👉 Pair programming

👉 Planning game

👉 Test-Driven Development

👉 Continuous integration

👉 Work/life balance

👉 Code refactoring

👉 Small releases

👉 Coding standards

👉 Collective code ownership

SCRUM

The devil of all developers

😈

1- How SCRUM works

3- What is each thing we need?

2- What do we need?

4- Rituals and anti-patterns

5- Scrum myths

1- How SCRUM works

1- How SCRUM works

2- What do we need?

👪 Team
📋 Product Backlog
📃 Agreements

1- How SCRUM works

3- What is each thing we need?

2- What do we need?

👨‍💻 DEV Team

Multidisciplinar group of people who can develop, deliver and deploy to production all kind of User Stories

🧐 Product Owner

Decides which way should the product go. He prioritizes the Product Backlog and motivates the team

🤴 Scrum Master

Ensures the team lives agile values and principles and follows the processes and practices the team agreed they would use

1- SCRUM Team

A list of tasks that:

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

👉 Has no low level tasks (no implementation details)

The team should agree on:

3- Agreements

✔️ Requirements for a task to be considered

✔️ Requirements for a task to be considered finished

✔️ When do the meetings

Anti-patterns

The company decides when to do the meetings

There is no definition of ready or done

Scrum Master

Anti-patterns

Sprint cycle of 2 weeks without reason

Product backlog no defined

Sprint changes definition

🧐 Product Owner

👨‍💻 DEV Team

🤴 Scrum Master

Creates & prioritizes

Develop

Promotes and assures

📋 Product Backlog

🎁 Product Increment

💞 Agile values

👪 Scrum Team

1- How SCRUM works

3- What is each thing we need?

2- What do we need?

4- Rituals and anti-patterns

Rituals

🗣️ Daily meetings

🏁 Sprint planning

📝Grooming

Meetings that have to be celebrated in order to do SCRUM.

🎉 Sprint review

🛡️ Retrospective

🗣️ Daily Meetings

Know the status of the sprint and the team

1. What I did yesterday
2. What I will do today
3. Is anything blocking me?

🙅 Bad Practices  in the Daily Meetings

Implementation details. Alert!!

Off-topic conversations

Technical conversations finding solutions

Reporting to the Product Owner

💁 Tips

Cut things fast. Break wrong habits. Ask for focus

Have to talk something? Do it later.

Make a circle

🏁 Sprint Planning

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

🙅 Bad Practices  in the Sprint Planning

Setting unrealistic expectations

Don't have a prioritized backlog

The Product Owner decides how much work

💁 Tips

Break tasks into smaller tasks. Dividi e vinci. 

Check tasks complexity the spring before.

Ask for a constant Product Backlog prioritization

📝 Grooming

Update the Product Backlog

👉 The PO and some of the DEV Team

👉 Add/Remove Stories

👉 Estimate tasks

👉 Update old tasks

Backlog refinement

🙅 Bad Practices  in the Grooming

Big estimations at the top of the Product Backlog

Tasks not estimated

Too much details for each estimation

💁 Tips

Use timers for each task 5 min top. Sometimes, 3 min extra

Question Stick. Who has the stick has to ask. Then pass it.

🎉 Sprint Review

Show the product increment to the stakeholders

👉 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!

🙅 Bad Practices in the Sprint Review

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

💁 Tips

Each team should present their User Stories.

Ask for challenges.

Use timers.

Team should only present working software

🛡️ Retrospective

Analyze and improve as a team

👉 What went well

👉 What can be improved

👉 Actions for next sprint

🙅 Bad Practices  in the Retrospective

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"

💁 Tips

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

🎉Retrospective time!!🎉

1- How SCRUM works

3- What is each thing we need?

2- What do we need?

4- Rituals and anti-patterns

5- Scrum myths

Myth 1. Scrum is easy

Myth 1. Scrum is easy

Scrum is simple, not easy

Myth 2. Scrum phases

Myth 2. Scrum phases

There is no Sprint of Testing

An sprint is a whole project

Myth 3. Sprint demo

Myth 3. Sprint demo

If I it had a User Interface you would see something here... here... and here.

In Scrum there is no "demo"

Myth 4. Team's commitment

Myth 4. Team's commitment

Is stupid. Usually it takes more than expected. Is irresponsible

People don't know this.

There is a Scrum Guide

https://scrumguides.org/scrum-guide.html

If what you are doing it's not there, it's not Scrum

Myth 4. There is no quality

Myth 4. There is no quality

Bonus-Driven Development

We've got money from the future

In Scrum there is quality,

but companies don't want it

1- How SCRUM works

3- What is each thing we need?

2- What do we need?

4- Rituals and anti-patterns

5- Scrum myths