Previously
A composer
A boot
A pizza!
Today, I try to make sense of it all
... and stick around to the end for your free Cheat Sheet
Welcome to Development That Pays
My name is Gary Straughan
And welcome to the 5th and final episode of Agile to Waterfall and beyond.
If you missed any of the previous 4 episodes and you'd like to catch up, click on this link
It should bring you Auto-magically back to this point
We started way back in Episode 1 by looking at this process
Note sure this it conforms to any recognised Agile framework,
It's iterative.
Very iterative.
It was the right approach for my level certainty with the process at the time.
And do you know what, it got the job done.
Inefficient, Yes.
But iterating towards a finished product meant there were no surprises.
Which is more than I can say about the process that replaced it.
By moving the steps around, I found I could remove the waste
An iterative process became a waterfall process.
Was it waterfall?
Mike Jones wasn't sure.
"you are still following some Kanban practices such as single piece flow - you are only working
on one video at a time."
Mike, you're right.
As waterfall processes go, it's about as watered down as it could be.
But even then, I had pain points.
- the part that I find difficult... became more difficult
(Remember we talked about Cognitive Load)
- the part I liked... became unpredictable
Sometimes it was as smooth as silk.
Sometimes it was a car crash.
I now look at these SYMPTOMS as indicators...
that I wasn't ready for waterfall.
"Waterfall works well for processes that are well-understood."
As yet I haven't reached the right level of understanding... in video production.
But pizza production
That's another story
A pure Waterfall process.
And batch sizes of up to... err... three ... are no problem for me
By the way, Mozart's ability to compose an entire piece... and then write it all down.
"As if he were just taking dictation"
Is a reminder that it's not about
the intrinsic difficulty or complexity of a task,
It's about our experience/understanding of the task
And FINALLY
This is the process I use now.
Is it a recognised Agile framework?
Kanban, perhaps?
On second thoughts:
"A new episode every Wednesday"
A Sprint?
Maybe it's Scrum.
Did you notice the dotted lines.
These loops are the LAYERS I talked about last time.
Once around I and have my "margharetta" video
Next time around...that's my pepperoni video
Around again.... there's my American Hot.
Hmm.
finishing a task...
taking another from the backlog.
That's sounds to me
like KANBAN!
If you've made it this far, you deserve a t-shirt.
Alas, I don't have a t-shirt for you.
But I do have a Cheat Sheet.
A Waterfall vs. Agile cheat sheet.
Around this video, you'll find a link.
Click the link,
Follow the instructions... grab your copy.
Now...
At the time of recording,
the Cheat Sheet is more "margharetta" than "quarto staggioni"
I need your help with the toppings:
So once you get your copy, come back here and let me have
your comments and suggestion for improvement.
I'll update it from time to time and send you an shiny new version.
So go on, grab it now.
And I look forward to talking to you next time...
which I promise will about something - ANYTHING - other than
PIZZA!!!
Thank you very much for watching.
If you liked this episode, please give it a thumbs up
Share it with your network
and click the logo
for a brand new episode every Wednesday.
See you next time.
Cheers for now.