Re:Agile as Trauma
by Zigurd on Sunday October 17, 2021 @05:27PM
(#28899951)
Start with why Agile was created in the first place: The formalisms of critical path analysis and waterfall project planning did not work well for most software projects.
Why? Because software is often entirely new, contains no repeating tasks, Therefore schedule risk is high compared to other kinds of projects.
Agile gives a team flexibility to assign tasks to team members for each iteration. While legacy project management styles entail frequent replanning because you can't do a proper resource-leveled critical path analysis without a plan for resource deployment. Agile is not as precise about projections of project completion, but you know that precise scheduling is not possible for a lot of software development.
Agile gets slagged for wireframe-driven development. If your view of Agile is colored by people drawing pictures instead of understanding data and functional requirements, that's not why Agile was created.
Why? Because software is often entirely new, contains no repeating tasks, Therefore schedule risk is high compared to other kinds of projects.
Agile gives a team flexibility to assign tasks to team members for each iteration. While legacy project management styles entail frequent replanning because you can't do a proper resource-leveled critical path analysis without a plan for resource deployment. Agile is not as precise about projections of project completion, but you know that precise scheduling is not possible for a lot of software development.
Agile gets slagged for wireframe-driven development. If your view of Agile is colored by people drawing pictures instead of understanding data and functional requirements, that's not why Agile was created.