Tom Jenkins, the newly appointed PMO manager convened his team. Xavier, Paula
and Xing were eager to start work. Tom explained that the PMO rollout is a
change process. He gave his team assignments around stakeholder analysis,
mapping of communication requirements, and creation of the PMO newsletter.
While the team was somewhat puzzled with these activities they moved to
fulfill them. Working with the stakeholders, the team captured many
complaints pertaining to the current way of work and gathered numerous
requests for improvements. Eagerly awaiting their next meeting, which was
held virtually through a videoconference, they prepared a list of proposed
improvements. Xavier proposed to commence work on the work breakdown
structure and the software development lifecycle. Paula suggested to update
the risk register template and to implement a new tool for project
The first step in building support within the greater stakeholder community
is identifying the various stakeholder groups and individuals impacting the
project/activities and analyzing their attitudes. Identifying stakeholders
can be completed alone or with a small team. Since analyzing them is a
sensitive undertaking, it makes sense to perform the activity with the kernel
project team, ensuring the output of the analysis remains within the team.
The objective of stakeholder analysis is to produce a list of stakeholders
that might influence the outcome of the project. Once the lis... (more)
This article depicts the best practice approach for integrating Agile
approaches and specifically Scrum development with traditional overarching
linear approaches, specifically waterfall methodology. The agile PMO,
properly defined, can be positioned to secure Agile-Scrum benefits while
maintaining the necessary overarching control.
Over the last two decades, various Agile approaches have been introduced and
practiced. Of these, in last 5 to 7 years, Scrum has gained the most
popularity resulting from a combination of simplicity, ease of use, and
effective public r... (more)
In a Scrum-Agile project management environment, the product owner acts as a
catalyst of change in the organization, enabling value creation through
projects and products. Product owners create the required link between how
the business would look like in the future and the current state. The product
owner is a key facilitator within the organization in bridging the client and
the business community with the Agile development team.
Most of what a product owner performs can be defined in the broader sense as:
1) Creating and increasing value for the business, and 2) Eliminating and... (more)
In order to create the combination between top-down problem-decisions
(waterfall like approaches)and local problem-decisions (Agile project
approach) here are practical guidelines to pursue
Three practical complex decision-problems guidelines:
Simple local rules Strategic top down rules Visual problem view
We describe in detail, each practical guideline, below.
Simple local rules
This cannot be overstated. Local rules must be easy to follow. Whether these
are rules for: a machine operator, traveling salesperson, a project
coordinator, or you packing your bags.
The local decision r... (more)