Initiation Document
Website for the Virtual Project Leader
Background:
AnyStandard.net is trying to establish a series of sites that will help out the Business
world. To complement the other sites AnyStandard.net, StandardSolution.net, SDLC.us,
and VirtualBusinesAnalyst.net this will be another tool for the Business World tool-belt.
Project Definition
Purpose:
Build a website of a Project in progress. This will benefit the Business world by giving an
example of how a project will be developed. What forms need to be done. What
procedures should be followed. A site ready for reference so when someone else needs to
do a project they can refer to this and make sure all elements have been covered.
Projects have been done before but may be slightly different in the approach. A standard
approach is what is always strived for. Why not have a model and stick to it. The desired
end of this project will be a useful tool for the next project in the business world.
Objectives:





Help out the Business World.
Create useful documents relative to a Project.
Create a site with easy to navigate pages and circular association.
Allow this site to be updated but maintain its original idea and show the progression of
change.
Track suggestions and document why or why not the suggestion was approved or taken
into consideration.
Scope:
The scope of this project is on a moderate scale. This will be developed using a simple drag
and drop software that is easily maintainable by the developer. Entertain ideas from any
viable source. Using agile project management release what can be published with the
understanding that changes can be made to what was published.
Project Definition (Continued)
Deliverables:
A working website, Product Initiation Document, Project Plan, Milestones, Gantt charts.
Constraints:
Resource Constraints
Key staff resources will be available only on a part-time basis.
Delivery Constraints
Deliverables submitted for approval will require working days for review.
There is no limit to review and approval cycles.
Environmental Constraints
None
Budgetary Constraints
Outside consulting requirements cannot be accurately estimated if deemed necessary
Functionality Constraints
The project depends upon receiving data from other, external suggestions.
Assumptions:
Many looks to this site may occur as requests and suggestions come to the project.
Business Case
Project Benefits:
This is one more site that will help expose AnyStandard.net. It is also a great tool for the
business. It will help describe the process of a Project created, executed, and
implemented. A great reference for anyone setting up a project plan. As more projects are
created, a standard approach can be replicated,
Options:
This is just a suggestion as a proven approach. You still have full discretionary power.
Cost and Timescale:
The cost of this project will only be the cost of my time. As far as a Time scale. The
availability of my free time. I project this to be finished in about 3 months.
Cost/Benefit Analysis:
Any time I spend on this project is well worth the effort. This can be referenced for years
which well exceed the time I’ve spent
Risk Analysis
Risk Identification:
Expected details in the Feasibility Analysis
Risk Prevention:
Throughout the whole project the Business Analyst will work closely with the Scrum Master.
Each will have best interests for both the business and the Project Leader
Risk Management:
Process handled during the Sprint Project Meeting
Risk Monitoring:
Process handled during the Sprint Project Meeting
Roles and Responsibilities
Project Leader






Leadership
Decision Making/Judgment
Knowledge of project
Planning timeframe with allocation of resources
Influencing all team members/ and key stakeholders support the project.
Communication of project
Business Analyst







Assessing the impact of the change
Capturing and documenting requirements
Delivering requirements between relationships
Deliver effective solutions with a good business plan
Provide tangible business benefits
Manage change across the whole business
Following the process all the way through of the SDLC
Product Owner





Define the features of the site
Decide on release date and content
Be responsible for the profitability of the product
Prioritize features according to market value
Adjust features and priority every iteration, as needed
Scrum Master






Represents management to the project
Responsible for enacting Scrum values and practices
Removes impediments
Ensure that the team is fully functional and productive
Enable close cooperation across all roles and functions
Shield the team from external interferences
Roles and Responsibilities (Continued)
Scrum Team

Cross-functional:
o Developers
o Testers
o User experience designers
o Scribe
Project Organization Chart/ Structure Diagram
All staff members are part of the IT department
The only exception is the Business Analyst who reports to Corporate.
Names of
Project Sponsor
Stan Standard
Project Manager
Bill
Business Analyst
Robert
Project Team
Product Owner . Paul
Scrum Master. Janet
Scrum Team
Bob
Jesus
Kim
Mark
Paul
Raghid
Sue
Initial Project Plan
Assignments/Milestones
Initiation Document to be completed by w/e 9/6
Feasibility to be completed by 9/8
Analysis, Design, and Development of 1st sprint to be completed by end of September.
Schedule (Gantt Chart)
Human Resource Requirements
Project Team:
Support Staff:
Additional Staff:
Project Control
Monitoring mechanisms:
Communication channels and Schedules
Quality Control