Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That description of "pizza-box development" (unfamiliar term for me) sounds pretty good actually? Seems pretty agile: informal planning, time-boxed sprint, revisit with stakeholder, repeat. It gets so much worse when the implementers are further from the stakeholders or customers. What's the issue there?

I've also worked in consulting and appreciate the explicit requirements, but I find the formality much less efficient than the process you describe earlier. It ends up being very "waterfall" and exactly the approach the Agile Manifesto attempts to counter.

Perhaps you prefer a more waterfall, hierarchical development process, or the companies (big ones) or industries (highly regulated) that necessitate it?



Buy a pizza for the devs, rip off the lid, sharpie draw the sprint on the lid while eating the pizza.


As long as the next pizza lid doesn't contradict the last one, that sounds like a good early-stage startup process!


Even if it does, it means we’ve learnt something in the middle. And at least the first box was in production.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: