Do we have to wait until after the project is delivered and handed over to operations to see if it was a good investment? This article will provide practical advice and a proven user research process you can use today to improve your benefits realization management .
18 items found
To build better applications, citizen developers need to learn how to analyze and design for enterprise risk requirements as a part of capability development.
Many project managers set project objectives without properly understanding customer needs, often resulting in failure. It’s your job to understand what the customer wants: a glass half full or half empty.
The Olympic rings are five intertwined circles that represent the elaborate and complex Games. Similarly, project managers can bring five rings of discipline together to manage very complex projects. Each of these rings builds upon the other--and they give the project manager a taxonomy by which to manage Olympian efforts
There is a need for every functional organization to establish a PMO. This will enable these organizations to streamline their project management processes—and allow projects to align with the overall objectives of the organizations.
In an Agile project, you don’t create large documents to hold user requirements; in fact, you don’t need a traditional document at all. The preferred technique is to use a product backlog, which represents a prioritized collection of work remaining on the project at any given time.
Especially in agile programs, the program architect and the program manager work together to provide business value to the organization. It’s difficult, intense and fun...and full of some myths that need clearing up.
Fixed contractual restrictions like timelines, budget and scope can be impractical on the Agile project. Here, Agile thought leaders Rachel Weston and Chris Spagnuolo share some ideas for breaking through the “iron triangle” during the contract phase of an Agile project.
Combining agile and governance seems, at first glance, to imply boxing people in from each perspective and forcing them to chose an option that is neither fully agreeable to each. But this combination is in the best interest of both camps; learn some practical approaches to make it work.
Adult children. Jumbo shrimp. Seriously funny. I’m sure you recognize these expressions as oxymorons — self-contradictory phrases, often with an ironic meaning. Should we add “agile requirements” to the list? Does agile development fit in with traditional requirements practices? And if so, how?