Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.
Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.
We require that our copyright notices are left in place.
![Martin Fowler aptly identifies Scientific Management as the root of plan driven work. Throughout his commentary, Martin implicitly rejects the application and governance of implementation management over the work of Agile software developers.
Martin eloquently nails the difference in the nature of work: that implementation work is plan driven; that Agile [a discovery approach to creating software] is adaptive.
Martin clarifies that: autonomous teams that do the work, [not implementation management & standard process], know best how to do the work [of software development]
In his rejection of the rule of implementation management, Martin doesn’t appear to be saying that management isn’t needed – it’s more like, management needs to stop imposing a plan-driven system onto work that is fundamentally adaptive and people/interactions driven.
However, Agile Practices do not amount to a creative management system as they lack management system properties (i.e. development of staff, governance, motivation, etc.):
Who trains autonomous teams, and when is a team ready to be granted autonomy?
Who governs, who determines when a team is out of control, and who fixes that?
Who motivates/inspires the team, who designs and awards appropriate incentives?
Hence, to the frustration of many Agile Founders, implementation management often awkwardly fills the void of having no creative management system in many companies. Dimension #1 – Conclusions of Agile v. Plan-Driven. ©2018 iiSM.ORG, All Rights Reserved.](/material-assets/software-management-essentials-intro-management-systems/dimension-1-conclusions-from-agile-vs-plan-driven-comparison-r2.jpg)