I think the most important area which we should spend time work on it , is the scope of the project , I found in most of projects , the scope is not definefd well Is there any points need tobe consider when er need to write the scope ? Saving Changes...
Before scoping any project:
Understand the business requirements - business analysis is required, document the requirements in a Statement of Requirements [SOR] document [business analyst should do this. Verify the requirements with the business [hold meeting with your stakeholders]
More discussions with your technical teams, gain their input
Amend the Statemeent of Requirements document and get it signed-off by your stakeholders [business]
Conduct any other meetings that you see as beneficial.
Scoping becomes easy - it is not about completing a template, it is about documenting the business \ projects scope correctly and accurately.
Vasoula Saving Changes...
HEMAM RANJIT KUMAR SINGHFounder & Director| TechSure Global Consultancy LLPGuwahati, Assam, India
I think since year 2007 , there might be some changes in the Project Scope Management Process , which is now at Page # 105 , as per PMBOK Guide Fifth Edition.
There is actually a process named "Define Scope" which is the process of developing a detailed description of the project and product.
1) Run a detail functional specification session where you collect Customer requirements
2) During this session register in an excel file all open issues, decisions and action items, for each one of these items include an owner and due date
3) For Open Issues on top of step 2 include also an assumption to close the open issue when the due date has been achieved without an answer in that way customer / supplier will understand the level of urgency
4) In a continuous processo update this matrix and share with the the audience
5) dont forget the Minutes of Meeting Saving Changes...
Quality professionals refer to QFD by many names, including matrix product planning, decision matrices, and customer-driven engineering. Whatever you call it, QFD is a focused methodology for carefully listening to the voice of the customer and then effectively responding to those needs and expectations.
Saving Changes...
saurabh mahajanPMP, ITIL, PRINCE2| vodafonePune, Maharashtra, India
all have given the best of the ways to gather requirements for defining scope. My little input as below
i think there should be rounds of collecting requirements
1) an informal meeting to get customer expectation
2) then a formal story writing in which customer/business analyst writes a need for customer
3) meeting with stakeholders to get their voice
4) formal requirement collection from stakeholders
after these iterations you will see some points (need,issue,problem) which might be repeated. These repeated points will constitute the basis of scope. other requirements will then revolve around these points. This will make defining scope more helpful as you now surely know the core (core requirements from project) of project.
Saving Changes...
arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
You need to check with the Business Owner on the project scope: what's in and what's out. Try to chunk your project in manageable pieces so that you can better manage the scope and deliver them quickly. Saving Changes...
Scope is the base of all project plan development. If the boundaries of the project are not established, the plan will always remain weak. Project scope can only be established if the product scope is understood and that is only possible through deliberate requirements gathering and information. Requirements cannot be effectively gathered until and unless we have a business case and identity of all stakeholders from whom to collect that requirements. So if we follow PMBOK guidelines, we can effectively establish scope for our project.
...
1 reply by Suhail Iqbal
Jan 09, 2016 2:59 AM
Suhail Iqbal
...
Remember scope is developed in two parts, first the Product Scope and then the Project Scope. Requirements lead to defining the Product Scope which can then be broken down into Work packages thus defining the Project Scope. Product Scope is measured against Requirements while the Project Scope is measured against the plan.
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Scope is one dimension you need to control on your project. Sometimes it is not the most important one to the client. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Defining the scope well is very important as well as all other plans. I advise you go through the PMBOK as a guide to prepare a very well detailed plan. Saving Changes...
Community Champion
