project plan

list

Lessons learned

where

when

who

HR

Staff skills

what

internal

chat

email

phone

Detailed

Initial

Project Team recognizes value in Agile approaches, and will implement high-bandwidth communication between team members by aligning with meeting structure and frequency according to the best practices of Agile management.

external

Initial

Detailed

Business Need

What will happen to the client if project is not undertaken?

the Client may reevaluate Business Need in view of the project initiation findings

e.g.

Why was the project initiated?

A Canadian non-profit needs to have its website upgraded. If this project is not undertaken, the client will lose revenue from lost sales and membership.

Constraints

The Client is constrained to have the project fully completed by October 20XX. Any later delivery will result in lost sales and publicity for the Client.

Alternative Solutions

Social Media

How the product fits into the organization's strategic vision

e.g.

e.g.

why

It is important for the individuals doing the work to have some knowledge of the business case in order to understand the client’s needs and expectations.

e.g.

website + admin + payment processing + mailing list, etc.

Consider

Big Design Upfront

Emergent Design

Software development processes

The completed product will be a website which consists of a public front-end and a secure back-end. The front-end will have the following features:

Member Registration

A separate page that contains a form with fields for the profile information. Allow possibility for a two-stage registration and use of third parties for authentication (Facebook, Google, Twitter).

Consider possibility to have the registration form on marketing campaign landing pages, as an app in Facebook, and so on.

Contact Form

Separate page

Storefront

Ability to select packages, and a secure checkout page where customers may enter their payment details.

Responsive Design

Further, a secure back-end that can be used to perform these administrative functions:

Milestone Schedule

Lock in design

Integrate design with PHP code

CMS functionality

Shopping Cart

Payment Processing

Backstore

The necessity to dismantle parts of the legacy system, and to reproduce their functionality in the Product introduces a degree of uncertainty.

Poor communication and unclear project goals can cause large features to be added forcing unsafe schedule compression, and technical debt.

The Client may have the expectation to replicate the legacy system with newer technologies. Besides the developments in technology, since the legacy system was built, the consumer attitudes and behaviour have changed, and so did the nature of online commerce. Due to the maturing and proliferation of APIs and other services, the current online business model is a lot more modular with a strong trend towards maximum decomposition of monoliths.

Lack of acceptance of the tools and protocols can introduce communication problems, defects, and deteriorated performance

e.g.

skip meetings

take shortcuts

fail to properly document work

consider

mitigate

Schedule Activities Associated w/Risk

A continuous risk management practice will be implemented. Known and potential risks will be continuously entered into the Risk Register document which will detail Risk Causes, Risk Triggers, Risk Impact, and a Risk Response Plan for each of the identified risks.

v2

Schedule Management Plan

Accuracy levels

Schedule Model Development

why

Produce sufficient guidance for the Development Team to do work during the current Iteration.

the insights provided at the weekly Review meeting may impact the requirements for the next cycle

external factors may necessitate a change in direction

maintain connection with the business reality

rapidly respond to change

Provide insight, and improve accuracy of projections for the Stakeholders.

Discover risks

Threats

Opportunities

Adjust deadlines or budget

what

Iterative process

Requirements are gathered and discovered continuously throughout the project

avoid excessive detail

A great number of requirements can only be known through assessing existing code

Committing to a detailed set of requirements makes course adjustments more costly, and leads to missed opportunities.

Having committed to a set of requirements, a team stops looking for ways to increase business value

Requirements Traceability Matrix

Traceability Matrix

categories

Business

Stakeholder

Solution

Functional

Nonfunctional

Transition

Project

Quality

Milestone Schedule

Establish Scope, Lock-in Resources, Internal Prototype

Develop & commit to a mockup. Integrate the the look with the codebase

Deploy Rapid Development Environment. Establish Procedures & Protocols

Basic Member Management

Basic CMS

Produce a functional prototype.

Complete the main member interactive areas of the website

A functional Admin Section. UI for data management. Member account control. Working CMS.

Produce a stable, usable version. Allow for partial deployment.

Front-end technical features & design specs complete. Implementing UX & UI feedback.

Admin Section tested by future users. Implementing feedback.

Full data exchanges between datacenters simulated. Gradual transition of services.

A Release Candidate. Full redundancy with live system.

UX metrics, analytics, marketing & SEO tools

Front-end CMS training & documentation complete

Admin Section running alongside WIMPS on live data. Training complete

Activity Resources

Sequence Activities to determine predecessors & successors

PHP the right way

Dependency Management

Build Automation

Development

Staging

CI

SCM

git

GitFlow

Consider JS framework for backend

The Development Team has the final say as to what tools they will use to complete the activities

continually refine

estimates

scope

Iterate

The project Client is the organization that commissioned, and will accept the completed Product. The Client can be represented by anyone who speaks on behalf of that group.

The project Stakeholders are all individuals that will use the completed Product.

The Project Team consists of all individuals who perform recurring activities on the project.

The Development Team consists of the members of the Project Team that are employed by Syspark.

The Product is the implementation of the product description in the Statement of Work section, built by the Development Team in close collaboration with the Client.

The project has full support of the Project Team and the Client

The methods and approaches outlined in this document are acknowledged by the Project Team and the Client as the framework for this project.

For clarification of questions regarding the process and methodology, the Project Team agrees to align with the best practices of Agile methodologies.

Méthode agile

we don't want to go in blind

address risks

focus intention

goal

objective

organize autonomously

flock of ducks

implement mechanisms for

Transparency

Inspection

Adaptation

milestones

velocity

communication