William M Hayden JrAdjunct Assistant Professor| University at Buffalo, School of Management, Operations Management & StrategyBuffalo, Ny, United States
Background:
A project by definition starts with the scope, schedule, and budget contractually in place.
And the client/owner waits to learn of progress on a scheduled basis, e.g., Monthly update.
Software development starts when the client/owner financially funds the needed resources and actually is embedded within the work group daily as they progress.
And at week's end, if client/ owner wishes, the software development continues for that next week.
There is no such thing as an "Agile Software Project."
I would strongly disagree on your underlying assumptions.
1) In a situation where change is urgent, a project may be launched prior to a firm schedule or budget. It may simply be deemed as something that must be done due to the consequences of doing nothing.
2) Software development starts at the definition of the problem statement and there is often significant development of conceptual architecture and feasibility before full funding and resources are addressed. Saving Changes...
You are presenting one possible pattern for software development work whether it is structured as a project or as ongoing product evolution.
I do, however, agree with your assertion that there is no such thing as an agile <anything> project, nor is there such a thing as agile project management. We can utilize adaptive approaches, tools, techniques or lifecycles, but that does not make the function of project management "agile" or a project "agile".
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You question is simple to answer. Go to the Manifesto for Agile Software Developement and read this https://agilemanifesto.org/history.html. Unfortunately most of the people do not read and understand the whole Manifersto and mainly the part I am referencing to. Saving Changes...
