A project is:
"a set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations." — "What is a project? definition and meaning". BusinessDictionary.com. Retrieved[masked].
The problem: Product development cannot be constrained to "certain cost" and products do not have a prescribed end date – so long as the organization finds innovative ways to meet market demands, the products they develop will evolve.
So, why all the projects?
I teach Scrum, Kanban, and Agile Engineering Principles and Practices – these are process frameworks used to manage complex product development. I find it so interesting that:
~55% of the people in my classes are "Project Managers"
~90% work daily in "project teams" and
~0% are ready to let go of Project Charters!?
Project charters in a complex problem domain such as IT and Software Development, but also all ‘knowledge work’, create only the illusion of safety, certainty, and confidence. But the practice is wholly inappropriate in knowledge work for one simple reason: the nature of our work is complex and therefore it is not possible to predict a "set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations".
Most attendees at this Meetup have worked in enterprises with authoritative Project Management Offices and “shared services”, but the real world exhibits tremendous diversity. It’s not difficult to find organizations with no PMO and not a single Project Manager, particularly among technology Startup companies. Let’s explore those alternative models together.
Strong opinions are welcome!!