The technique used to identify and scope an enterprise's value streams and the customers it serves. Used in conjunction with Event Analysis and Customer Satisfaction Analysis, this technique identifies all interactions between the customers of the value stream and the enterprise, the responses, the activities required to satisfy...
The purpose of this step is to invent the processes that will constitute the new value stream(s). The BRE team incorporates the proposed solutions from breakthrough into new, reengineered processes f...
The purpose of this step is to gain consensus of the assessment of the current value stream between the BRE team, the Steering Committee and the Reference Group(s). In this assessment, the BRE team p...
What signals help you tell different kinds of AI work apart—and what tends to go wrong when everything gets lumped together?Have you ever been in a conversation where “AI” meant different things to di ...
Hi PMI Community! I’m Sarah Philbrick, and I work as a Product Manager at PMI with a focus on our learning offerings. As we go on this skill-building journey together, I’m excited to engag ...
A common question that we hear a lot is “Why choose Disciplined Agile Delivery (DAD) over Scrum?”, so we’ve written this blog to summarize our response. The shor ...
Question:I’m an agile lead working with a traditional project manager on a hybrid project for an outside customer. Each time we all three meet, the PM brings out so many risk charts—and explains the potential pitfalls and recent statistics in such a negative way and with such an emotional tone and facial grimacing—that the customer is almost panicky when he leaves. Agile is all about embracing the potential for risk, but how can I speak to someone on my peer level about changing his behavior and message so that the customer feels appropriately informed while still confident in the team and our progress when he leaves?
A.
Agile teams may work for some types of small software projects. However, other projects cannot possibly be completed successfully without careful preparation and constant monitoring of analysis checklists, risk registers and SWOT analyses. The information gathering techniques and diagramming techniques can also deteriorate the project if the correct ones are not implemented.
B.
The suggestions in A Guide to the Project Management Body of Knowledge (PMBOK® Guide) are only intended to be suggestions. In reality, no actual projects use them. Instead, a project manager will have the highest percentage of successful undertakings by simply relying on the already existing practices found in the organization. They are the reason this enterprise thrived in the first place.
C.
You need to talk to your co-lead on this hybrid team about being on the emotional payroll and why his current behavior is not good for the project. It’s uncomfortable talking to a peer about this, but it is better than the entire project failing or the customer experience being negative and thwarting future contracts with this client.
D.
Since agile and traditional project management are so different, you two should take turns meeting with the customer for the updates. In this way, you won’t have to witness the behavior that you find unacceptable. If the customer does panic at the unconsciously scary message of doom and gloom delivered by your colleague, he can take it up with his boss.
Disciplined Agile Delivery (DAD) offers a comprehensive, knowledge-based approach to delivering agile projects that are operating in complex technical and enterprise environments. This case study shows how a retrospective analysis of a real-life project that was delivered for one of the UK’s largest retail banks uncovered real potential for process improvements.
Intending to transform the established life insurance business of a leading insurer is a multi-dimensional challenge. It is also a story of the level of adaptability, perseverance and collaboration. In this case study of a leading Swiss insurance Company, the author shares the insights gained from the four-year journey as the company prepares for implementation.
Scenario: A particular software development project is underway, but progress is slow, even with the required resources on board. Technical issues are compounded by changing requirements, and planning is complicated by development resources getting pulled into support work on existing products. Quality has been compromised. The problem described above is an example of what we view as a work process issue. This is in contrast to what we have called, in a companion paper ("IT Project Management: The Role of Governance"), a governance issue.
"There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened."