Posts Tagged ‘stakeholder’

Project Management: Cost ‘n’ Price Relationship

Friday, June 12th, 2009

One of the things that we believe to be important for project management is the proper understanding of the relationship between cost and price. In this post we will try to clarify the meanings for these two words.

Price is the amount of money or something valuable that a customer is ready to pay or give in order to receive something valuable from you. In terms of software project management, the thing that the stakeholder receives is the project being done, and the things that the customer and stakeholders receive are the results of the project – be it either goods or services. Money is what usually paid for doing the project. At the same time, Cost is the amount of resources (equipment, materials, money, people, etc) that are utilized in order to produce goods or services, the deliverables of the project.

(more…)

What is Project Charter Document

Monday, April 13th, 2009

Any of our projects start their life as soon as Softheme’s project manager creates a formal document called the project charter. The latter is a small document prepared to state the project name and the purpose of the project. It should also contain other important project-related information, namely, the business case for doing the project and a rough schedule and budget for the project. Besides, it should describe the needs and expectations of the stakeholders and list the assumptions and constraints that are recognized at the current point in the project.

(more…)

Project Scope Management: Softheme View

Wednesday, April 8th, 2009

In the next several posts we would like to discuss the basics of scope management since it is one of the most important parts of project management which we at Softheme pay special attention to. Due to proper application of scope management approaches to the projects of our clients, Softheme is so successful and productive in delivering projects of various complexity levels. So we believe it would be useful to share our experience regarding this matter.

Scope management is a starting point for any project

However, with web being a more dynamic sphere of development, we believe that scope management is better applicable to application development which usually requires a more thorough approach.

It is needless to say that the most common reason behind project failures is poor scope definition. This means that the expectations of the stakeholders, mainly of the client or sponsor, and the expectations of the project team are quite different. Being a most difficult problem, it is nevertheless critical to the success of the project. Projects fail due to many reasons, and understanding them does a good job in helping to avoid failures.

(more…)

SWIT Investor Day