Thank you, Glorious Leader!
If you could explain Agile with pizza I'd appreciate it!
So you want a pizza. You sort of know what a pizza is but not sure what is the process of making a pizza to eat. But thats not going to stop you and so you start the process.
Welcome to Agile where the goal is fuzzy and the scope is clearly not even thought about but there is already a timeline. In this case, you need to make a pizza before you starve to death.
After all how hard can it be, your sure there are code segments I mean ingredient lists you could borrow on Stackoverflow.
And so you start you grab some flour and pour it into a bowl.
Then you add some beer as beer makes everything better.
It really is a sticky bubbly mess but it seems to be shapable and so you spread it out. Then put it into the oven to bake. But what comes out is not very tasty as reported by your QA tester.
And so you start again.
Days pass as you try different amounts of mixing, different liquids, different flours, different oven temperatures and cooking time. Each iteration gets you closer to a pizza crust that will work for your pizza. Someone on Stackoverflow suggests that yeast is needed and that it should rest for hours between the mixing and cooking. Someone else mentions that beer also has yeast and so it should work too. Hopefully, you'll finish the crust by the end of your two-week sprint and then can pick up the next task which is pizza sauce.
