What is a Project?
Joshua Barnes
I help organizations, leadership, and teams improve value delivery with agile, lean, hybrid, and value stream management.
How can an organization get its hands around all of what is needed to deliver value to customers?
Ask a selection of your colleagues or LinkedIn connections what they think a project is, and the answers you get may vary quite a bit. For example, just over a week ago, I had a great discussion with @Steve Tendon, the creator of Tameflow, and @Ian Heptinstall, a Lecturer in Project Management at the University of Birmingham, UK.?
The discussion started with Ian sharing thoughts and experiences of his first contact with Agile about two decades ago.?Ian’s thoughts - most of what agile was bringing to the world is just good project management.?
The discussion touched on what a project is. Whether an agile way of working
I ask you to picture the flow of work
领英推荐
What about the other value-adding activities that may also need to take place??Was there an earlier project to determine what the value to the customer would be and then approval to move forward??What about any supporting areas of the organization
Ian led us into this part of the discussion by calling all of the work to get value delivered to the customer a “Work Package.”?In Discipline Agile, we now have the Minimum Business Increment (MBI), and in Tameflow, there is the Minimal Outcome – Value Effort (MOVE).?Ian, Steve, and I shared our perspective on all three of these, and I feel we arrived at a very similar point. They are containers to describe everything, at a high level, that needs to be done for that value to be delivered.
In my opinion and experience, the MBI is one of the most critical additions to Disciplined Agile.?As a container of information, it bridges communication through the value stream
Disciplined Agile MBI, Tameflow MOVE, or Ian’s Work Package - there is a growing awareness of how organizations can shift from siloed projects
Disciplined Agile | Gest?o de Projetos | Agilidade | Lideran?a
3 年Excellent discussion, Joshua!!
PMBOK-7 co-writer. Dr. Computer Science. IBM - Project Management. PMI Authorized Training Partner Instructor for PMP and Disciplined Agile. Consultancy, Management, Training, Software, AI, DevOps, Cloud, Agile, Lean.
3 年A temporary endeavor to realize a unique product, service, or result.
Architect of Organizational Excellence| Driving Executive Success and Team Cohesion
3 年Not sure I understand “Whether an agile way of working or serial/predictive way of working” as it seems like a false dichotomy. 1. Agile should be delivery predictably. 2. Waterfall has a proven track record of being predictably unreliable. So the entire premise of the comparison is false. A project, by definition, is a short-term effort by any entity engaged. It is a temporary effort which will not be supported by the team(s) developing it. Anything else is a Product.
AI & Bias PhD Researcher | EdTech Award Winner | MIT | AI & PM Contributor | PMP | EU Advisor | Peer Reviewer | Founder
3 年This is an interesting approach Joshua. Thank you for sharing. You refer to a very strong aspect related to MBIs and the different value streams that they convey: development value stream (IT), supporting value stream (marketing, legal, etc.), enabling value stream (infrastructure, procurement, etc.), and operational value stream. This is what make MBIs applicable not only to IT product development but also to other industries. It would be really interesting if you could bring this topic to one of your online discussions with Steve Tendon and others.
Managing Partner, Valense Ltd. | Strategic Consultant | Author | Speaker | Team Coach | Dyslexic Thinker
3 年Joshua Barnes, thank you for this, I really enjoyed the discussion with Ian and Steve and look forward to more of those. I have been reflecting on the link between projects and agile for quite some time and this is my take on Work Packages and MBIs. (I am not familiar with MOVE, so will not comment) Work packages can be of various size; it is the point at which the project manager delegates work and the lowest level of work they directly manage. Each work package comprises one or more activities. A work package’s OUTPUT is a specific deliverable, or MVP. The OUTPUT, once used by operations, becomes a CAPABILITY, a MMF (Minimum Marketable Feature) in a DA context. This CAPABILITY/MMF generates OUTCOMES (Minimum Marketable Release (MMR) in DA) that are associated to user stories. In my opinion, the MBI is the BENEFIT, a positive outcome that adds VALUE. Outcomes and MMRs are a set of features that addresses needs, whereas the MBI, or benefit, should generate value for the organization. See also https://www.dhirubhai.net/feed/update/urn:li:activity:6821129816301998080/