assignment 81

Project-based learning How to approach, report, present, and learn from course-long projects

Harm-Jan Steenhuis and Lawrence Rowland

Chapter 7

Projects that contribute to practice

Practice process

Setting expectations, help manage customer

Customers and Deliverables

• A characteristic for projects that contribute to

practice is that it deals with the customer.

• Besides the product being produced for the

customer, the project also needs to produce

“project” deliverables that communicate the

project to the customer.

• Each process in the lifecycle has its own

“project” deliverable for the customer.

“Project” Deliverables

• Initiating – Charter

• Planning – Plan

• Executing – Progress reports

• Monitor and Control – Progress reports

• Closing – Lessons learned

These reports support communication between the project and the customer.

Anticipate a project document to

support each process no matter what

lifecycle is selected.

Initiating – Charter Outline

Topic Sub-topic

Background Client strategy

Business case

Product/project description High-level objectives

Outputs and activities

Team

Schedule (milestone dates)

Assumptions/risks

Resources needed

Team policies

Communication plan

Sign-offs

Planning – Plan Outline

Topic Sub-topic

Introduction

Business case

Project scope WBS

WBS dictionary

Team members Roles and responsibilities

Responsibility assignment matrix

Schedule Network diagram

Gantt chart

Resources

Communications

Stake holders

Risks (optional)

Quality (optional)

WBS for Product Proposal Plan

WBS for Product Proposal Plan

Further Decomposition of Business Case

1.2 Business case

1.2.1 Business documents review meeting

1.2.2 Business requirements draft

1.2.3 Stakeholders requirements draft

1.2.4 Solutions requirements draft

1.2.5 Review of drafts

1.2.6 Draft revisions

1.2.7 Final draft submission to report

Using the WBS

for:

1.2 Business case

1.2.1 Business documents review meeting

1.2.2 Business requirements draft

1.2.3 Stakeholders requirements draft

1.2.4 Solutions requirements draft

1.2.5 Review of drafts

1.2.6 Draft revisions

1.2.7 Final draft submission to report

1.2.1 Business documents review meeting

1.2.2 Business requirements draft

1.2.3 Stakeholders requirements draft

1.2.4 Solutions requirements draft

1.2.5 Review of drafts

1.2.6 Draft revisions

1.2.7 Final draft submission to report

1.2.1

1.2.2

1.2.3

1.2.4

1.2.5 1.2.6 1.2.7

Roles

Sequence

Schedule

Executing/Monitor and Control –

Progress Report

Topic Sub-topic

Introduction

Update Business case

Changes to WBS, team, and/or resources

Schedule Update

Tracking Gantt chart

Progress Report – Tracking Gantt Chart

Closing – Lessons Learned Outline

What worked well What can be improved

Requirements definition and management

Scope definition and management

Schedule development and control

Team development and performance

Communication management

Stakeholder management

Reporting

Process improvement information

Product-specific information

Other

Lessons Learned

Project title: _____________________ Date prepared: _____________________

Agile or Adaptive Approach

Sprint

Planning

Sprint

Review

Sprint

Retrospective

Daily

Scrum

Sprint

Cycle Increment

Sprint

Backlog

Product

Backlog

Adapted from Schwaber and Sutherland, 2017

Communicating project results -

Keep it engaging and professional!

(Not like this)