Scribd
Upload
54 views10 pages

Lesson 2.2 Business Planning

This document discusses business planning for software projects. It outlines three key activities for business planning: determining objectives, proposal writing, and forecasting demand for the product. For determining objectives, the document states that the function, cost, and price objectives as well as project team objectives need to be established. Proposal writing involves creating an executive summary, statement of need, project description, and budget. Forecasting demand involves quantitative, qualitative, casual, and time series methods. Requirements analysis allows understanding and documenting customer needs through tools like mandatory/optional requirements, ranking, and risk analysis.

Uploaded by

B
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
54 views10 pages

Lesson 2.2 Business Planning

This document discusses business planning for software projects. It outlines three key activities for business planning: determining objectives, proposal writing, and forecasting demand for the product. For determining objectives, the document states that the function, cost, and price objectives as well as project team objectives need to be established. Proposal writing involves creating an executive summary, statement of need, project description, and budget. Forecasting demand involves quantitative, qualitative, casual, and time series methods. Requirements analysis allows understanding and documenting customer needs through tools like mandatory/optional requirements, ranking, and risk analysis.

Uploaded by

B
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Click to add text

Chapter 2 - Session 2
Learning Objectives
• Understand the methods of business planning in a project
Business Planning

• The planning process determines how all the assets of the company will
be marshaled to achieve the goals and objectives.

• Business planning has three key activities which are determining


objectives, Proposal writing and forecasting demand for the product.
Business planning(determining objectives)

• The function, cost, and price objectives for a software product


need to be determined.

• Also, the objectives of the project team developing the product


need to be stated.

• The only way to get to a particular goal is to know what the goal is.
Business planning(Forecasting demand for the product)

• In some environments, a software product is developed on speculation


that there is a market for the product.

• It is necessary to know what the potential market for the product may be
before committing large amounts of venture resources to the project.

• There must be ways to forecast the demand for the product.


Business planning(Forecasting demand for the product)
cont’d
• Quantitative Assessment Method takes numbers or quantities sold in the past to forecast
how much will be sold in the near future.

• Qualitative Assessment Method is based upon how customers and experts think or feel a
product will sell.

• Casual Methods work under the assumption that underlying incidents can affect sales
numbers of products and services. E.g. holidays and seasons that boost sales of certain
items.

• Methods Using Time Series A time series is a series of data points indexed in time order.
Most commonly, a time series is a sequence taken at successive equally spaced points in
time.
Business planning(Proposal writing)
In many environments, a contract is sought with an organization or the government. This is
usually initiated by a request for a proposal(RFP).

The components of a proposal are:


• Executive Summary – umbrella statement of your case and summary of the entire
proposal.
• Statement of Need – why this project is necessary.
• Project Description – nuts and bolts of how the project will be implemented and
evaluated.
• Budget – financial description of the project plus explanatory notes.
• Organization Information – history and governing structure of the non-profit; its primary
activities, audiences, and services.
• Conclusion – summary of the proposal's main points.
Business planning(Requirements analysis)

• This phase/stage allows us to understand and document customer needs.

• There are tools and techniques that allow to understand and classify
system requirements.

• Examples of the tools:


• Mandatory and Optional requirements.
• Ranking.
• Value Analysis.
• Requirements Risk Analysis.
Requirements Analysis (tools and techniques)

• Mandatory and Optional - Many analysts categorise requirements as mandatory or


optional.
• Ranking -Ranking is a useful tool when only limited resources are available.
• Value Analysis - Which requirements contribute the greatest part of the value?
• Requirements Risk Analysis - identifying requirements that introduce risk to the
project and deciding whether you should drop them as a way of avoiding the risk.
• Kano Analysis - identifying what is going to delight a customer if delivered, and what is
going to leave them dissatisfied if not delivered.
• Stakeholder impact analysis - Different stakeholders have different views on what is
important.
References
Project Management Managing IT Projects to PMI Standards(Belgium
campus textbook)

https://www.pmi.org/about/learn-about-pmi/what-is-project-manageme
nt

https://dictionary.cambridge.org/

You might also like