Methods
Questions You'll Answer
What is Agile?
Is Scrum what you do when you're Agile?
Wait, Agile is not just implementing Scrum?
What is waterfall and why do people fall back to it?
What about Lean • LeSS • Kanban • Spiral • Xtreme Programming • Shape Up?
How do I apply xyz method in my team?
So what if I apply xyz method in my team if other teams don't?
I can't refuse my boss, and my boss just wants to look at GANTT charts, timelines, and fixed requirements!
What You'll Learn
Feel even more lost navigating the world of "agile"
Get upset realizing you spent $4000 paying for a Certified Scrum Master / Product Owner
Notice when people spout nonsense and attaching keywords like agile and waterfall
Know the limits of implementing methodologies when the organization is structurally incapable
Feel confident rejecting "daily standups" from ScrumMaster-wannabes
Hard Truths
Everyone says agile this, agile that as buzzwords to sound clever, without trying to define it or making sure others share that definition.
Non-technical folks hear agile and they like the phrase, because it sounds smart, and they quote that often too even when everything about their work remains the same.
Estimating requirements accurately at the beginning is an impossible task, but that's the expectation of most public service budgetary processes.
Despite the obvious drawbacks, public sector organizations like the comforts of waterfall and continuously revert to waterfall practices.
Predictability of scope, cost, timelines are key draws of waterfall approaches.
Employees who get their organizations to sponsor huge sums to send them for Scrum, Kanban courses end up exactly the same after those courses, which begs the question what the point was in the first place.
There's little point trying to implement Agile, Kanban when the structures, processes of the organizations actively resist alternative approaches to developing working software.