6 ms·

What alternatives have people come across? I know there is waterfall: months of planning followed by months of implementation, followed by a single deployment a

What alternatives have people come across? I know there is waterfall: months of planning followed by months of implementation, followed by a single deployment at the very end. Then there is the gradient of in-betweens along the line of scrum to waterfall. I've not encountered any other methodologies yet.

n42 4y ago
Shape Up seems to have been gaining traction: https://basecamp.com/shapeup/webbook https://basecamp.com/shapeup/webbook in my opinion, it feels more like agile than Agile™
buescher 4y ago
There's more than one AGILE methodology. SCRUM is only one of several. Probably if you're doing SCRUM you're using techniques from some of the others, so you might not see the distinction. Look 'em up. KANBAN, for example. A whole lot of organizations, particularly gelled teams at them, do some variation of "plan, iterate, ship": https://blog.pragmaticengineer.com/project-management-at-big-tech/ https://blog.pragmaticengineer.com/project-management-at-big... AGILE consultants did not invent iterative development, by the way. I have never seen any process actually followed that looks like the AGILE consultants' caricature of "waterfall". The more serious you get, though, about defining requirements up front and making sure you meet them, the more your process will look like traditional systems engineering and stage gates. This does not preclude iterative work - the buzzword decades ago was the "spiral model".
mch82 4y ago
XP - http://www.extremeprogramming.org/ http://www.extremeprogramming.org/ ShapeUp, as n42 commented - https://news.ycombinator.com/item?id=31534642 https://news.ycombinator.com/item?id=31534642 Product Development Flow by Don Reinertsen - http://reinertsenassociates.com/books/ http://reinertsenassociates.com/books/ Queueing Theory - https://en.m.wikipedia.org/wiki/Queueing_theory https://en.m.wikipedia.org/wiki/Queueing_theory

n42 4y ago

Shape Up seems to have been gaining traction: https://basecamp.com/shapeup/webbook https://basecamp.com/shapeup/webbook in my opinion, it feels more like agile than Agile™

buescher 4y ago

There's more than one AGILE methodology. SCRUM is only one of several. Probably if you're doing SCRUM you're using techniques from some of the others, so you might not see the distinction. Look 'em up. KANBAN, for example. A whole lot of organizations, particularly gelled teams at them, do some variation of "plan, iterate, ship": https://blog.pragmaticengineer.com/project-management-at-big-tech/ https://blog.pragmaticengineer.com/project-management-at-big... AGILE consultants did not invent iterative development, by the way. I have never seen any process actually followed that looks like the AGILE consultants' caricature of "waterfall". The more serious you get, though, about defining requirements up front and making sure you meet them, the more your process will look like traditional systems engineering and stage gates. This does not preclude iterative work - the buzzword decades ago was the "spiral model".

mch82 4y ago

XP - http://www.extremeprogramming.org/ http://www.extremeprogramming.org/ ShapeUp, as n42 commented - https://news.ycombinator.com/item?id=31534642 https://news.ycombinator.com/item?id=31534642 Product Development Flow by Don Reinertsen - http://reinertsenassociates.com/books/ http://reinertsenassociates.com/books/ Queueing Theory - https://en.m.wikipedia.org/wiki/Queueing_theory https://en.m.wikipedia.org/wiki/Queueing_theory