Skip to main content

Characteristics of successful projects



I recently came across that a well reputed PM guru has explained that he "believes that the triple constraint, as we know it, may have to be customized to add a value part for these nontraditional jobs and the traditional received value measurement system will be replaced with a value measurement methodology. very well

What he might be getting at is nice that there are two principal standards for task success. Is the traditional triple constraints based standards and the other is the value that the project result brings. Absolutely nothing new here.

Don't More than Simplify!

Let's not over simplify by merging those two together and making the PM feel as if she should be understanding the product and making portfolio management decisions.

The project manager offers "products". While the PM could possibly influence the value produced from that product, this individual or she usually has little input or control. Project manager performance is mostly measured how well project scope, cost and time objectives have recently been met.

Of course there is also criteria, including the degree where the PM can collaborate at the program and stock portfolio level, coach and advisor, build strong relationships, and so forth But these without meeting objectives are irrelevant.

What is Worth?

Value is the identified impact (positive or negative) of the project as well as its results on the firm as well as its environment. Did the product make or save money? Did it eliminate or enhance the physical and emotional environment?

Established on the PMI model, value or benefits would be the focus of the program. This distinction is centered on the recognition that operational use is often far more complex than product delivery. In functional use there are clients, users, support people and systems, relationship managers, and so on. managing ongoing activities. The ongoing nature of businesses and use adds higher complexity because it suggests adapting to change within the organization, in the market or in the wider environment, over an extended time-frame.

The PM Role

The PM should certainly be aware of and educated about the business and organizational implications of the project. The PM is more than the usual simple man of art; he or she must consider the business and architectural work related to the project. In this way, as much as it is possible, the project manager can affect project decisions in light of the permanent value perspective.

There is a tough balancing act among the trades-offs between permanent value and short term delivery time and cost. It requires leadership from above the Project Management. This software manager, sponsors, product executives, marketing, sales and businesses managers, and client ombudsmen must be in charge of providing value. In this dominion, the only point of responsibility is not the PM.

Comments

Popular posts from this blog

Leading Managers Using Latest Resource Management Software

There are numerous resources available to a company a manager has to effectively coordinate in order for the company to succeed. These resources may include manpower, funds and information technology. Prior to the creation of resource management software, managers a new hard time designating the various resources to the diverse projects that the companies were willing to undertake. During this period, the managers worked in an environment that was packed with paper. It was at times inconvenient when it came to looking through these papers to gain access to the kind of information. It was irritating and time wasting for managers. This concern and the complexity of the resource management contributed to the introduction of affordable resource management software that has greatly aided in boosting the way that the managers synchronize and allocate these resources. This has gone a long way in boosting the efficiency and accuracy and reliability of the managers as well as ensuring max...

Lessons Learned: Improving Your IT Professional Services Automation

I can’t tell you how many times I’ve heard people voice their frustrations about how badly their IT project management processes suck because every project is just as painful as the last. It makes you want to grab project managers by the shoulders and say, “Dude, if you want your next project to go more smoothly, you actually have to DO Lessons Learned exercise. You know that, right?” Not sure how to go about doing Lessons Learned the right way for your project? No worries, I’m here to help you. A few weeks ago, I came across a great article called, “ IT - Professional Services Automation ” that does an excellent job of laying out the basic for IT - Professional Services Automation. Improving as we do things: You don’t need to wait for the project to end to have the Lessons Learned meetings. Meetings organized as the project progresses can bring fabulous ideas that help the ongoing project. If you’re doing things thoroughly, each status meeting should include a brief sec...

Scrum vs Waterfall

Relatives Sizing Of User Reports (Scrum) Tee-Shirt Sizes. Intended for release planning we might use estimates of comparative size. When less is known about the consumer stories (features or requirements) for a release, we can estimate by using a wide brush approach. Based upon such standards as how intricate we think the end user story is, how much effort it will take, and the unknowns or doubt, we give it a tee-shirt size (XS, S, M, L, XL). We can then compare all the user tales and assign relative sizes. For example, we can take one user history and based on the above conditions assign it a tee-shirt size of "Large. " We are able to then compare all the other stories against this "Large" size and assign the relative value of each story. This relative size estimating can ensure that the product owner (business representative) choose user reports to prioritize for a release. Story points. We all can then assign each tee-shirt size story factors based on an ir...