Using the Concepts and information provided in the Project Case and the Killer Bots Attack Charter document build me a Charter for a Software product of your choice. Have only three members of the Stakeholders, You, and two others.

Business Charter: Killer Bots Attack

Introduction:

The initial project has been approved by the gaggle of students now known as The Group.

This Charter will define how we plan on going forward with the project.

Success Defined:

• The game will be completed within the time and financial frames established by The Group.
• There will be no more than a 10% overage in both time, development and implementation of the product going out into the market.
• All variations or changes will be approved, validated, and funded prior to implementation of the change.
• The Group will evaluate the final product for all its established aspects and will make the final decision on its viability and if it meets our guidelines.
• The Group will agree on success with a minimum of 75% approval from all member of The Group, and dissenters will be required to give reasons or rationale for their descent.
• Final Decision for release is if all The Group agree to it, and understand the ramifications if we do not release.

Measureables:

• Our project objectives will be measured using standard industry parameters in terms of developments.
• Time Boxing or Sprint types of development objectives and measures will be in place.
• Each development team will follow the established guidelines for development within their Sprint.
• Story Boarding will the basis for most development Sprints.
• We will breakdown all Sprints and other development efforts into approvals by milestone or by the functional code in a release condition (As defined further in this document).
• What are the requirements at a high level/overview;
  • Functionality and story boards have reality and meet intent/guidelines.
  • Testing confirms functionality
  • Integration with earlier functional code is required and maybe via a Sprint

Project Description: Killer Bots Attack mobile game

Our first product developed by The Group is

• Fun,
• Mobile,
• Easy to play,
• Mind numbing, and
• Simple
• Our Goal is to capture an audience and then expand on it.

Characteristics:

Our initial concept is a simple, loadable game for mobile devices. It should not take a lot of memory or processing power to use it and it should minimize the power requirements used as well.

• We will construct, or the user will build an army of deranged zombie like bots that will attack and try to take over the world via villages, towns, cities, states, nations and eventually the whole world.
• We will not limit our bots to only eating brains. Some zombie bots will get brains and will become smarter, others arms or legs and will gain those attributes.
• The ability of the bots will be limited and they can only accomplish their goals if they find ways to get around obstacles by gained intelligence, brute force, working together or a combination of all three attributes.
• We will have hidden escape routes for all the people in the above mentioned locales so multiple battles can occur between the saved and the eaten.

Other characteristics will be launched during our final development meetings before the initial development and during review meeting before and after each development Sprint.

• Add layers of complexity as add-on or next gen products
• Initial, beginner, Brunch, Second Breakfast, Lunch, Medium level, Advanced, Expert, and OMG
  • Overhead

Milestone Schedule:

See the attached Gantt chart. This will be an integral part of the project management and one member or several members of The Group will be tasked to make sure will stay on schedule using this management tool.

(Insert example of the Gantt chart here)

Budget:

We will (The Group) establish a strict set of guidelines for development, marketing, sales, and administrative expenses. The Group will meet no less than weekly to review all expenses.

Expenses covered will include the following at a minimum:

• Development teams
• Members of each team
• Computing requirements expenses
• Legal
• Accounting
• Marketing
• Sales
• Contracted costs

These will be tracked via a time line chart so we can see both the minute by minute expenses as well as the overall final expenses via three to six lines culminating in as final as built cost for every segment, Sprint, and the final the project expenses real time or no later than with one week delays.

Questions to ask and answer relevant to our budget?

People:

• Who are the people we need? However the more important side of that question is:
• What are the skills we need to be successful!
• What knowledge base can we start with?

Materials:

What kind of materials do we need to get started and what will we need long term?

• Computing power, desk space, white boards,
• Software, Physics engines, other graphical design software
• Are there specialized equipment that will allow us to succeed? Cray XP1 as an example?

Money

• To Start
• To Run
• Define context of these ideas
  • Leader or leadership group within The Group

A separate set of members from The Group will monitor track and keep all members with budget guidelines. Budgets will be time, money, and materials based. (Checks and Balances)

Defined Roles:

• Project Manager
• Development Lead
• Team Leads, Sprints, Segments,
• Operational lead
• Financial lead

Each member in a Lead position will define their goals, objectives and focus for their position and the position of each member in their team.

Cross training is critical for success and must be accomplished

What are the roles and responsibilities and the basic duties to be performed by:

The Project Manager:

Sub groups/working teams from the The Group

Architects of the game:

Analysis and Design Group/Team

Algorithm Group/Team

Graphics Group/Team

Sound and music development Group/Team

Integration Group/Team

Business and Legal Integration Group/Team

• This team will also be in charge of the official name of the Product

Authorization Scheme: Who can authorize expenditure/money or other resource utilizations such as materials, and manpower increases or decreases.

The Group

• Required to authorize all dollar amounts above $10,000.00

Project Manager

• Authorization for amounts up to $5,000.00 and with the Sub group/Team Leaders form $5,001.00 up to $9,999.00

Sub Group/Team Leaders

• Authorization for amounts up to $4,999.99
• Group Members plus an Authorization Leader from $0.00 up to $1,000.00

The Original Group members

• Authorizations from $0.00 up to $1,000.00 Up to a maximum of the groups budgeted amounts.
• Non-Original Group members are not authorized to spend funds.
  • The Original Group Members also known as the Thursday 13

Authorization Leaders are: The Project Manager, Sub Group/Team Leaders, and The Original Group Members

Stakeholders are:

• The Project Champion will be selected by The Group and will serve for the entire project unless one of the following happens:
  • He or She resigns from the Project
  • The group votes to remove the Champion by a unanimous less one (1) vote

Dissolving relationships:

Any member may leave The Group or the Project at any time given the conditions described below:

• Member decides to leave
• Member is asked to leave

If either of the two above conditions occur, then the member leaving forfeits:

• All funds contributed,
• Any stock options provided,
• Any guarantees of any kind
• All acknowledgements of being involved with the Project.
  • Money above $100.00

Change Management:

All changes that require additional funding, or other resource allocations must be authorized by the appropriate Group, Sub Group/Team Leaders up to the limits established by the Authorization paragraph above.

Amounts or other conditions of significant change in resource utilization must be resolved by The Group.

Once the project is underway the change management procedures will be fully described and a log of all changes above:

• Time above budget or above one week
• All Increases of manpower
• All materials required above the initial allocation provided by/for each Sub- Group/Team

The Group also known as the Thursday 13 will meet every Thursday and

• Establish progress reporting documents as well as deliverable statements.
• This meeting will be held in the kitchen/conference room at 10 AM local time.
• Any member wishing to make comments or statements or deliver information and is not in attendance will be allowed to do so using Skype or other such teleconferencing software

(Insert the Change form example here)

Funding Requirements:

Funding Requirement from each member

Tier 1 - Initial Investments with a minimum of $50,000.00

Tier Two investments of no less than $500,000.00

First Round Finance from Investors no less than $500,000.00

Second Round Investor funding no less than $1,000,000.00 with a minimum group of five (5) investor groups.

Third Stage Investor groups

Once the above has been defined, analyzed and evaluated then The Group will authorize or not authorize this charter.

Name and date by each member of the group formally named as The Group.

1.__________________________________ ________________ Appr/Not Appr

2.__________________________________ ________________

3.__________________________________ ________________

4.__________________________________ ________________

5.__________________________________ ________________

6.__________________________________ ________________

7.__________________________________ ________________

8.__________________________________ ________________

9.__________________________________ ________________

10._________________________________ ________________

11._________________________________ ________________

12._________________________________ ________________

13._________________________________ ________________