Lesson 2

Download as pdf or txt
Download as pdf or txt
You are on page 1of 8

Project Activities?

Software Project Management consists of many activities, that includes planning of the project,
deciding the scope of product, estimation of cost in different terms, scheduling of tasks, etc.

The list of activities are as follows:

1. Project planning and Tracking


2. Project Resource Management
3. Scope Management
4. Estimation Management
5. Project Risk Management
6. Scheduling Management
7. Project Communication Management
8. Configuration Management

1. Project Planning: It is a set of multiple processes, or we can say that it a task that performed
before the construction of the product starts.

2. Scope Management: It describes the scope of the project. Scope management is important
because it clearly defines what would do and what would not. Scope Management create the
project to contain restricted and quantitative tasks, which may merely be documented and
successively avoids price and time overrun.

3. Estimation management: This is not only about cost estimation because whenever we start to
develop software, but we also figure out their size(line of code), efforts, time as well as cost.

If we talk about the size, then Line of code depends upon user or software requirement.

If we talk about effort, we should know about the size of the software, because based on the size
we can quickly estimate how big team required to produce the software.

If we talk about time, when size and efforts are estimated, the time required to develop the software
can easily determine.

And if we talk about cost, it includes all the elements such as:

 Size of software
 Quality
 Hardware
 Communication
 Training
 Additional Software and tools
 Skilled manpower
4. Scheduling Management: Scheduling Management in software refers to all the activities to
complete in the specified order and within time slotted to each activity. Project managers define
multiple tasks and arrange them keeping various factors in mind.

For scheduling, it is compulsory -

 Find out multiple tasks and correlate them.


 Divide time into units.
 Assign the respective number of work-units for every job.
 Calculate the total time from start to finish.
 Break down the project into modules.

5. Project Resource Management: In software Development, all the elements are referred to as
resources for the project. It can be a human resource, productive tools, and libraries.

Resource management includes:

 Create a project team and assign responsibilities to every team member


 Developing a resource plan is derived from the project plan.
 Adjustment of resources.

6. Project Risk Management: Risk management consists of all the activities like identification,
analyzing and preparing the plan for predictable and unpredictable risk in the project.

Several points show the risks in the project:

 The Experienced team leaves the project, and the new team joins it.
 Changes in requirement.
 Change in technologies and the environment.
 Market competition.

7. Project Communication Management: Communication is an essential factor in the success


of the project. It is a bridge between client, organization, team members and as well as other
stakeholders of the project such as hardware suppliers.

From the planning to closure, communication plays a vital role. In all the phases, communication
must be clear and understood. Miscommunication can create a big blunder in the project.

8. Project Configuration Management: Configuration management is about to control the


changes in software like requirements, design, and development of the product.

The Primary goal is to increase productivity with fewer errors.

Some reasons show the need for configuration management:

 Several people work on software that is continually update.


 Help to build coordination among suppliers.
 Changes in requirement, budget, schedule need to accommodate.
 Software should run on multiple systems.

Tasks perform in Configuration management:

 Identification
 Baseline
 Change Control
 Configuration Status Accounting
 Configuration Audits and Reviews

People involved in Configuration Management:

What Are Project Objectives?


A project objective is a statement that describes the “what” of your project. The
tangible and measurable “what”. The “what” that’s achievable, realistic, and can
be completed within the time allowed. These statements ladder up to the goals of
the project, providing stepping stones to success.

Why Are Project Objectives Important?


Project objectives are the guideposts when making decisions throughout the
lifespan of the project. They communicate project purpose in clear, tangible
morsels.
Project Goals vs. Project Objectives: Aren’t They The Same Thing?
Short answer: No.
The goal is usually a high level target set by the business which is the underlying
driver behind a project (and how they put the budget towards it).
The objective is the detailed outline of the big picture of the project. Imagine a
connect the dot diagram, the goals are the dots but the objectives are the
numbers. The objectives help direct you to the end result of the project.
Example

Goal Objectives
An increase of form completions by 5% in the first quarter.
Improved
Leads Implement validation to improve the quality of the leads captured in the forms
decreasing the number of false data by 10% in the first year.
Better UX Users can get to high profile content in three clicks or less.
The website will be inclusive and should meet WCAG2.1AA by 2020.

How to Set SMART Project Objectives


1. Use plain simple language
2. Use action words
3. Use numbers to quantify your objectives/dates

What Does SMART Mean?


SMART is an acronym that stands for:
S = Specific
M = Measurable
A = Achievable (or attainable, actionable, appropriate)
R = Realistic
T = Time-bound (or timely, traceable)

And here’s what each part of the SMART acronym means:


Specific
Make sure your objective is clearly defined. Narrow your scope of the objective so
that is has a very tangible and specific outcome. This helps you focus your intent.
When writing this part of the objective think of the Who, What, Where, When and
Why of it all.
Measurable
Make sure you can actually quantify the objective. If it’s not measurable, you won’t
know when the project objective has been met. You want to make sure the
objective is trackable to keep you and the team accountable.
Achievable
Make sure you can accomplish the objective. Identify the clear steps that need to
happen to make sure the objective is completed. When writing this portion of the
objective as yourself how you will accomplish it? What steps need to be taken in
order to accomplish the specific objective you’ve defined?
Realistic
This one is really important. Don’t set objectives that can’t be achieved within the
constraints of the project. Make sure your objective is practical. Do you have the
budget to do this? Is there enough time? Does your team have the right knowledge
or do you have time to invest in learning?
Time-Bound
When will this be done by? Having a clear end date defined helps everybody
involved. It lets you know when you need to focus on that objective. It also helps
you set a relationship between multiple objectives on a project as well. If you can’t
do objective C until A is done and A is getting done in Q1, then you should have C
completed in Q2.
Example 3

You might also like