Project Planning and Closing
Defining Scope, Quality, Responsibility, and Activity Sequence
Project Planning: The Next Step
Following the initiation phase, the next crucial step is developing a detailed project plan.
Planning addresses key questions:
What needs to be done?
How will it be accomplished?
Who will execute the tasks?
How long will it take?
What will it cost?
What are the potential risks?
Chapter Concepts
Clearly defining the project objective.
Preparing a project scope document.
Understanding the importance of planning for quality.
Creating a Work Breakdown Structure (WBS).
Assigning responsibility for work items.
Defining specific activities.
Creating a network diagram.
Utilizing the Systems Development Life Cycle (SDLC) for information systems development projects.
Learning Outcomes
Establish a clear project objective.
Prepare a project scope document.
Discuss the importance and elements of a project quality plan.
Develop a work breakdown structure.
Prepare a responsibility assignment matrix.
Describe how to define specific activities.
Create a network diagram.
Establish Project Objective
The planning process is based on the project objective.
Establishes what is to be achieved.
Often stated in the project charter or RFP.
Represents the tangible end product.
Project objective includes:
Expected benefits.
Primary project end product or deliverable.
Date required to be completed.
Budget.
Changes must be agreed upon by both the customer and contractor.
Define Project Scope
Project scope defines what needs to be done.
Includes items from the project charter, RFP, and proposal, providing more detail.
Establishes a common understanding of the scope with all stakeholders.
Project Scope Document
Usually contains:
Customer requirements.
Statement of Work (SOW).
Deliverables.
Acceptance criteria.
Work Breakdown Structure (WBS).
Establishes a baseline.
Implements a change control system to avoid scope creep.
Agile Project Scope VS Traditional Project Scope
What is agile project scope?
How is it different from a traditional project scope in project management?
How is agile project scope management, controlled?
How is scope creep managed in agile projects?
Plan for Quality
Complete work according to specifications and standards.
Plan for assuring quality as the project progresses.
Include:
References for specifications and standards.
Written procedures for quality tools and techniques.
Key aspects:
Monitor as the project progresses.
Do work right the first time rather than rework.
Create Work Breakdown Structure (WBS)
Deliverable-oriented hierarchical decomposition.
Organize project work and deliverables.
Create logical groupings.
Subdivide into more manageable components.
A deliverable is the output of a work package.
Resource requirements and durations can be assigned.
Accountability can be assigned.
Project manager can monitor and control.
Can be represented as a graphic chart or an indentured list.
Assign Responsibility
Use a responsibility assignment matrix.
Designate responsible individuals.
P = Primary responsibility.
S = Support responsibility.
Associate responsibility:
For each work item.
For each individual.
Only one primary responsibility per work item.
Define Activities
Responsible resources define activities.
Break down work packages into work items.
Define the level needed to perform each deliverable.
A comprehensive activity list is essential.
Activities may not always require expenditure of effort (e.g., wait time).
Sequence Activities
Create a network diagram.
Defines the sequence of activities and their relationships.
Serves as a tool for arranging the order of activities.
Common techniques:
PERT (Program Evaluation and Review Technique).
CPM (Critical Path Method).
PDM (Precedence Diagramming Method).
Network Principles
Activities:
Represented by a box.
Consume time.
Described by a verb.
Relationships:
Linked in a serial sequence.
Can be completed concurrently.
Loops
Represent an illogical relationship among activities.
Perpetually repeats itself.
Not acceptable in project planning.
Laddering
Involves laddering activities to allow for the shortest possible completion time.
Best use of resources, such as three workers or experts.
Represents a set of repeating activities in a serial sequence.
One work activity.
Two wait activities.
Can be performed simultaneously if sufficient resources are available (e.g., triple resources).
Create Network Diagram: Tips and Techniques
Establish a logical sequence of activities.
Show dependent relationships.
Elaborate as the project progresses.
Use subnetworks for similar activity sequences and relationships.
Questions to answer during diagram development:
Must one activity finish before the next can start?
Can activities be done concurrently?
Can any activities not be started next?
Guidelines for determining the level of detail:
Define each work package.
Draw a summary-level network, then add detail.
Add detail to the point where responsibility or deliverable changes.
Ensure the duration is less than the project progress review period.
Planning for Information Systems Development
Definition
A computer-based system that:
Accepts data as input.
Processes the data.
Produces useful information.
Examples:
Computerized order entry.
E-commerce.
Automatic teller machines.
Billing, payroll, and inventory systems.
Process
Plan, execute, and control.
Utilize the Systems Development Life Cycle (SDLC).
Problem definition.
System analysis.
System design.
System development.
System testing.
System implementation.
Project Management Information Systems (PMIS)
Wide variety of systems available.
Plan and control projects in interactive mode.
Plan and test different options.
Create reports, diagrams, and charts.
Interface with other software applications.
Additional information available in Appendix A.
Project Closing Actions
Collect and make final payments.
Recognize and evaluate staff.
Conduct post-project evaluation.
Document lessons learned.
Organize and archive project documents.
Final Payments
Payments from customers:
List the activity to perform collection.
Ensure that all payments have been received.
Payments to others:
Verify all payments have been made.
Record actual costs.
Account closing:
Perform a financial analysis of the project.
Compare actual costs versus the baseline budget.
Staff Recognition and Evaluation
End the project with recognition and celebration.
Recognize team members for their contributions.
Celebrate the success of the project.
Prepare individual performance evaluations.
Mention how knowledge expanded during the project.
Identify areas where further development is needed.
Share evaluations during individual meetings or give them to supervisors.
Post Project Evaluation
Review and evaluate project performance.
Identify improvements.
Hold individual meetings with team members.
Hold a project team meeting.
Prepare a written report with lessons learned and recommendations.
Lessons Learned
Purpose of identifying and documenting:
Capitalize on knowledge and experience gained.
Improve performance on future projects.
Create a knowledge base system or repository.
Retrieve lessons learned from prior projects.
Easily access information by category or subject.
Record keeping throughout the project.
Capture lessons at the time they are learned, instead of at the end of the project.
Include lessons learned as an agenda topic at meetings and in training sessions.
Archive Project Documents
Organize, file, and archive appropriate documents.
Organize the system to make information easily retrievable.
Create a database of common data elements.
Analyze elements for trends.
Examine records for bidding, planning, and performing future projects.
Customer Feedback
Hold a post-project evaluation meeting with the customer.
Determine if the project provided the expected benefits.
Assess the level of customer satisfaction.
Obtain feedback with open-ended questions.
Discuss future opportunities.
Secure permission to use the project as a reference.
Participants:
Key project team members.
Key customer representatives.
Project manager.
Post-Project Customer Evaluation Survey
Analyze for trends.
Seek permission for reference.
Critical Success Factors
Plan the work, then work the plan.
Developing a well-thought-out plan is critical to project success.
Participation builds commitment.
Involving individuals in planning increases their commitment.
The project must have a clear objective.
Defined in terms of end product or deliverable, schedule, and budget.
Must be agreed upon by the customer and the project team.
The project scope document is valuable.
Establishes a common understanding among stakeholders.
Having a quality plan at the outset is beneficial.
Helps prevent additional costs and schedule extensions due to rework.
Key to quality control:
Monitor work early and regularly.
The network diagram is a communication tool.
Shows responsibility for each activity and how each person’s work fits into the overall project.
Recognize the project team and celebrate achievements throughout the project.
Regularly ask the customer about satisfaction and take corrective action promptly.
Evaluate project performance after completion to learn and improve future projects.
Capture and document lessons learned throughout the project.
Establish a knowledge base of lessons learned and ensure its use on future projects.
Organize and archive project documentation and analyze key data for future projects.
Retain customer evaluation and feedback for developing future proposals.
Summary
The planning process is based on the project objective.
Establishes what is to be achieved.
The project scope defines what needs to be done.
The project scope document usually contains:
Customer requirements.
Statement of Work (SOW).
Deliverables.
Acceptance criteria.
Work Breakdown Structure (WBS).
The quality plan must include or reference specifications, industry standards, and codes.
The Work Breakdown Structure (WBS) establishes the framework for how the work will get done.
A responsibility assignment matrix defines who will be responsible for the work.
Activities define more specifically how the work will be accomplished.
A network diagram defines the sequence of how and when the activities will be performed.
Project planning is a critical activity in developing an Information System (IS).
The Systems Development Life Cycle (SDLC) is often used to plan, execute, and control IS development projects.
Numerous Project Management Information Systems (PMIS) are available to help plan, track, and control projects interactively.
Closing the project is the fourth and final phase of the project life cycle.
Staff recognition and evaluation are important project closing actions.
Conduct post-project evaluation meetings to gather feedback for improved future performance.
Identify and document lessons learned to improve future performance.
Ensure that project documentation is properly organized, filed, and archived.
Conduct a post-project customer evaluation to determine whether the project provided the customer with expected benefits and to assess customer satisfaction.
Projects may be terminated before completion for various reasons.