Agile & XP Series
Agile and XP as practised rather than certified: short feedback loops, pairing, and continuous everything.
6 parts
- 1
Update Your Team to Be More Extreme
How can you help your peers to embrace the change?
Our profession is constantly evolving; therefore, it demands a non-stop learning process. Embracing the change is not optional in our software industry. We need to create spaces to get out of our comfort zone.
- 2
Working Agile with Non-Agile Teams
How can you work with other teams that aren't agile?
Let's assume you already know what the agile manifesto is. Let's consider that you apply most of the extreme programming values, principles, and practices. How can you work with other teams that aren't agile?
- 3
Ignoring Scrum to Get More Agile?
Killing agility with excessive meetings
People become slaves to systems that are supposed to help. Boring meetings are killing agile. Meetings require active participation from everyone. Otherwise, you might not be essential to that meeting, and rather use your time with something else.
- 4
Deployments on Fridays
Why "should we not" deploy to production on Fridays?
I have heard multiple times, from various people, the idea of panic towards deploying on Fridays. How good is that idea of banning the day before weekend from delivering new value to our clients or customers?
- 5
What Kills Agility?
Why Agile if you already do Scrum, Kanban, SAFe, or Waterfall?
Why Agile, if you already do Scrum, Kanban, SAFe, or Waterfall? How we manage an organization defines its quality. Excellent management is crucial to avoid the Waterfall trap if we aim to build an Agile environment. But why would we want that? What's wrong with the way we already work?
- 6
Ship, Show, Ask
Match the review to the risk, not the ritual
Not every change needs the same review. Ship, Show, Ask matches the review process to the risk of the change, so teams keep shipping without losing quality or collaboration.