Amanda Logistics

AGILE METHOD SELECTION -SCRUM

RATIONALE - ASSUMPTION
•Project is timebound
•Impact in delay may lead profit loss to company
•Need to have feedback while implementing various hardware and
configuration
Pre-Project
Starting up a Project
Document: Project Scenario: Amanda Logistics
Company: Amanda Logistics
Amanda Logistics is a company in to IT service to remote customers. The company want to launch a project to address recent spike
in escalation calls from remote users. This is to increase quality of deliverable to remote customer and improve relationship. Reduce
escalation calls and increase brand name and business.

The Service delivery Manager chaired a meeting and the outcome of the meeting was as follows:
•Secure the firewall
•Architect the firewall zones and IP addresses
•Configure access control lists
•Configure the other firewall services and logging
•Test the firewall configuration

Project Scope
•Search good vendor on material procurementDefine quality requirements
•Choose right material procurement
•Complete the five step network configuration recommended
•Test and complete the project.

Out of Scope
•Original list of clients (will be supplied by accounts)
Project mandate
Document: Project mandate Project: Firewall migration & Author: Mathew Paul Date: 21.07.2021
Replacement project

1. Project Definition 3. Project Product Description

The project will choose implementation of actions and address escalation calls To be created from remote users.
Project Objectives 4. Approach

•Firewall update in the VPN Service

Do the project internally
•Removal of inconsistency in firewall settings
Project Scope:
1. Supplier list 3. Complete recommended configuration 5. Project Management Team

2. Order the material The Executive shall be the CEO

2. Reasons
Build better relationships with customer by good service
Reduce the loss in business
Project Management Team Structure (part of Project Brief)
Firewall migration & 21-07-2021
Document: Project Management Team Structure Project: Author: Mathew Paul Date:
Replacement project

Corporate or Programme Management

Senior User Executive Senior Supplier

Susan Kelly John King Terry Clinton
Balaji: CIO

Susan Kelly: Sales Manager Project Assurance Change Authority Terry Clinton: Purchasing & Accounts

Rose Carr: Customer Project Manager

Project Manager

Mathew Paul Project Support Revanth, cheery

Tailoring comments for the Project Management Team:

•The Project Manager will have the roles and responsibilities of Team Manager.
•The Project Board will have the role of Project Assurance.
•The Project Manager, Executive, Senior User, and Senior Supplier will have the change authority role.
•The management (Project Manager) and delivery (Team Manager) levels have been merged
Daily Log

Note: the content of this sample Daily Log belongs to next stages of the
project
Project Product Description ( Workshop)

The Project Manager hosted a workshop to create the Project Product Description. The main workshop
goals:
1.Get buy-in / lessons from the team / stakeholders
2.Complete the Project Product Description during the workshop
Requirements Exercise
•PM to give each person post-its and reminded them about the project goals
•Each person to list requirements
•After this exercise, the PM categorized each requirement and identified the top requirements
•The requirements are listed below using the MoSCoW technique

Prince 2 Agile -Project Amanda Logistics - Mathew Paul 01/08/24

Introduction to the quality information
Outline Business Case (part of Project Brief)
Project Brief
 Initiation Stage Plan
Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final)

Processes 

Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project
mandate
Daily Log, Lessons Log

Project Brief

Project Product Description

Project Management Team

Structure
Outline Business Case

Initiation Stage Plan

Initiation Stage Plan
Document: Initiation Stage Plan Project: Firewall migration & Author: Date: 21-07-21
Replacement project

1.Plan description 6. Tolerances

This is the plan for the Initiation Stage of the Project Time: ± 1 0 % Cost: ± 10% : Scope: 0%

2.Assumptions - Dependencies 7. Products Description(s)

Attached: Project Product Description
1. Vendor list is available for evaluate / procurement .
2. Trained personnel available for execution of this project 3. Schedule
3. Internal resources will be used for this project Deliverables - March 4th 5th 6th 7th 8th 11th 12th 13th 14th 15th
Approach documents
6 hrs
PBS (WBS)
4 hrs
Product Descriptions
8 hrs
Risk & Issues
4 hrs
4.Monitoring & Control Project Plan 3 hrs
Benefits Mgmt Approach
2 hrs
The PM will use the standard PRINCE2 documents Business Case
A highlight report will be sent at the end of week to the Project Board 2 hrs
An Exception report will be used if a stage forecasted to go out of tolerance PID
1 hrs
Next Stage Plan 2 hrs
•Budgets

Initiation stage budget: €200 (internal people time is not charged)

Risk Budget: €0, Change Budget: €0 This is a simple example of the schedule. Note: the focus is on the products created and not the activities
The pre-project activities are now complete and the Project Board may
give permission for the Initiation Stage to begin

Stage 1
Initiation (Planning)
Approx. 80% of the work in this stage is focused on planning (product breakdown, requirements,
product descriptions, estimating, scheduling)
 Communication Management Approach (part of PID)
Stage 3 (Final)
Pre-Project Stage 1 (initiation)
Stage 2

Processes
Starting 
up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project
mandate Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

There are four approach documents, these are guidelines for the project. Normally the
Four Approach Docs approach documents from standard
Project Product Description
in each company. There are
Project Management Team 1) The Communication Management Approach
Structure
2) The Risk Management Approach
Outline Business Case 3) The Quality Management Approach
4) The Change Control Approach
Initiation Stage Plan
Communication Management Approach (part of PID)

Document: Communication Management Approach Project: Firewall migration Author: Project Manager Date:

1. Introduction 6. Reports / Stakeholder Matrix

This document describes how communication will be done during the project: Report Name Timing Recipients
It is based on the standard approach document. Highlight Report Weekly End of Project Board Project
End Stage Report End Project stage End of Board Project Board
2. Communication Procedure Report Issue Report PM/Project Board
project
The PM is responsible for all internal project communication and will report Anytime
each week to the Project Board using a Highlight Report. Other documents and
reports will also be used as expected.
7. Roles & Responsibilities
Project Board Project Inform the rest of the management team All
3. Tools and techniques
Manager internal communication (project team) Create the
• The PM will use the intranet portal site for all internal communication and required PRINCE2 documents Communicate with
project documentation. Senior User clients

8. Scales: Priority & Severity

Priority Severity levels Use MoSCoW (Must, Should, Could, Wont..) 1 =
4. Records Project Manager, 2 = Project Board
The following documents will be used for internal communication
- Highlight Report, End Stage Report, End Project Report, Issue Reports, 9. Stakeholder Analysis
Lessons Report, Project Descriptions and registers
The PM is responsible for all internal project communication and will report
each week to the Project Board using a Highlight Report. Other PRINCE2
5. Timing of communication activities documents and reports will also be used as expected.
The PM and Project Board will meet each two weeks The Sales Manager is responsible for all external communication
The PM and Project Board will meet at the end of each stage
 Product Breakdown Structure (part of the next Stage Plan)

Stage 3 (Final)
Pre-Project Stage 1 (initiation)
Stage 2

Processes
Starting 
up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project
mandate Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

Four Approach Docs
Project Product Description

Project Management Team

Structure
Outline Business Case

Initiation Stage Plan

Next Stage Plan Note: this diagram only contains the
sample documents of this training course,
PBS rather than all the necessary documents in
each stage.
Product Breakdown Structure (part of the next Stage Plan)

Document: PBS for Stage 2 (hierarchy chart) Project: Firewall migration & Author: Muniarathinam Date:
Replacement project

1. Hierarchy presentation of PBS

Level 1: Firewall migration & Replacement project The Project Manager can create this kind a diagram using
Level 2: 4 groups of products
Project Post-Its with help from Team Members,
Level 3: List all the products in each group

Supplier Evaluation Procurement Installatio Testing

n
 Product Description(s) (part of PID)
Pre-Project Stage 1 Stage 2 Stage 3 (Final)
(initiation)

Processes 
Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project
mandate Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

Four Approach Docs
Project Product Description
Product Descriptions(s)
Project Management Team
Structure A Product Description can be created for each product identified
in the Product Breakdown Structure (PBS)
Outline Business Case

Initiation Stage Plan

Next Stage Plan
PBS
Risk Register
Document: Risk Register Project: Firewall migration & Author: Project Manager Date:
Replacement project

Project Name Project Risk / Impact

Project No 008 High Risk > € 3,500

Project Manager Muniarathinam Medium > € 1000

Project Executive John King Low Risk < € 1000

Risk Date Risk Probability x Response Risk Risk

ID Risk Description Proximity Status
Author Register Category Impact Category Owner Actionee

A risk that material will be delivered 2-4 weeks later

1 P Smith 6/3/20 Ordering which will impact the time of the project € 550 Stage 2 Reduce Active P Smith J Bell

Delay in installation and configuration

2 S. Kelly 7/3/20 Product € 3,760 Year 1 Reduce Active S. Kelly R Clark
Project Plan (part of PID)

Document: Project Plan (Part 1) Project: Project Author: Date:

1.Plan description 6. Tolerances

This is the high-level plan for the whole project. Time: ±10% | Cost: ±12% | Scope: MoSCoW

2.Prerequisites, Assumptions, and external dependencies 7. Products Description(s) Delivery Manager and CEO will provide the necessary time for

the project. Attached: Project Product Description Resources are available for the evaluation. Should arrive on time.
Evaluators will fill in the forms in time and precisely. 8. Schedule

The supplier will prepare the material in an appropriate time. Attached: Schedule for stage plan 1
Internal resources will not be charge to the project.
9. Product Breakdown Structure
3.Lessons incorporated
Allow buffer time for delivery

•Monitoring & Control

The PM will use the standard documents for reporting A Highlight Report will be sent each week to the Project Board
An Exception Report will be used if forecasted to go out of tolerance

•Budgets
Project budget: €1,840 (internal people time is not charged)
Risk Budget: €0, 0 days | Change Budget: €480.
 Business Case (part of PID)

Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final)

Processes 

Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project mandate
Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

Four Approach Docs
Project Product Description
Product Descriptions(s) Project Plan
Project Management Team
Project Controls
Structure
Outline Business Case
Benefits Management Approach

Initiation Stage Plan

Note: this diagram only contains the
Next Stage Plan sample documents of this training course,
PBS rather than all the necessary documents in
each stage.
 Project Initiation Documentation (PID)

Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final)

Processes 

Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project mandate
Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

Four Approach Docs Tailoring
Project Product Description
Product Descriptions(s)
Project Management Team
Project Plan Project Controls Business
Structure
Case
Outline Business Case
Benefits Management Approach

Initiation Stage Plan

Next Stage Plan
PBS
 This is the Stage Boundary process and it starts towards the end of
the current stage.

Stage Boundary
 Dependencies Diagram (part of the next Stage Plan)
Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final)

Processes 

Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project mandate
Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

Project Product Description Four Approach Docs Tailoring Tailoring
Product Descriptions(s)
Project Management Team
Structure Project Plan Project Controls

Outline Business Case

Benefits Management Approach

Initiation Stage Plan

Next Stage Plan
PBS
Dependencies
 Next Stage Plan

Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final)

Processes 

Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Project
mandate Risk Register, Quality Register, Issue Register
Daily Log, Lessons Log

Project Brief Project Initiation Documentation

Four Approach Docs Tailoring
Project Product Description
Product Descriptions(s) Project Plan
Project Management Team
Project Controls Business
Structure
Case
Outline Business Case
Benefits Management Approach

Initiation Stage Plan

Next Stage Plan
PBS Schedule
Dependencies
Summary
 Summary

Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final)

Processes 

Starting up a Project Initiating a Project Controlling a Stage Controlling a Stage

Managing a Stage Boundary Managing a Stage Boundary Closing a Project

Management Products 

Configuration
Project
Management
mandate Risk Register, Quality Register, Issue, Register

Daily Log, Lessons Log

Project Brief Project Initiation Documentation Issue Report End Stage Report Product Status End Project Report
Four Approach Docs Tailoring Account Lessons Report
Project Product Description Highlight Report Next Stage Plan
Product Descriptions(s) Project Plan Configuration PBS Schedule
Project Management Team Item Record
Project Controls Business Dependencies
Structure
Case
Outline Business Case
Benefits Management Approach Lessons Report

Initiation Stage Plan End Stage Report Work Package

Next Stage Plan Note: this diagram only contains the

PBS Schedule sample documents of this training course,
rather than all the necessary documents in
Dependencies
each stage.