Camosun College
Ancestor Project
Work Book
Author:
Creation Date:
Last Updated:
Version:
William Heaton, Jason Michael, Matt Donnelly
Wednesday 23, 2011
Wednesday 23, 2011
1.00
Project Meeting
Date: 11.1.11
Time: 15:00
Meeting called by:
Marla Weston
to 16:00
Type of meeting:
Weekly Progress
Attendees:
Marla Weston
Diane Biin
William Heaton
Matt Donnolly
Jay Michael
Please bring:
----- Agenda Topics -----
Item 1: Scope
Time: 3:00
to
Discussion:
What the project scope will entail
Conclusions:
Initial focus on a content management system and video tutorials
Action items:
Person responsible:
Page 2 of 53
Deadline:
----- Agenda Topics -----
Item 2: Sooke School and requirements gathering
Time: 3:00
to 4:00
Discussion:
Visiting the Sooke and Brentwood Bay Tribal Schools to aquire information on the requirements necessary from
the users themselves.
Conclusions:
Visit the school sometime this quarter and meet some students during the Science week.
Action items:
Person responsible:
Finalize the date for the Science week awards
Marla Weston
Page 3 of 53
Deadline:
Project Meeting
Date: 17.1.11
Time: 15:00
Meeting called by:
Marla Weston
to 16:00
Type of meeting:
Weekly Progress
Attendees:
Marla Weston
Diane Biin
William Heaton
Matt Donnolly
Jay Michael
Please bring:
----- Agenda Topics -----
Item 1: Year of Science awards
Time: 3:00
to 4:00
Discussion:
Surveying the students/teachers that took an Alice course at BBTC.
Talk to the teacher
Conclusions:
Listen to what the students say in terms of requirements
What content worked for the instructor.
How ill the server be set up?
Action items:
Person responsible:
Deadline:
Survey students
TEAM
25th Jan
Come up with questions to ask teacher.
Page 4 of 53
----- Agenda Topics -----
Item 2: Discussion of project reports
Time: 3:00
to 4:00
Discussion:
Need to get reports signed prior to Weds meeting.
Conclusions:
Action items:
Person responsible:
Deadline:
----- Agenda Topics -----
Item 2: Scope and available resources
Time: 3:00
to 4:00
Discussion:
Further discussion of scope and the resources available to the team.
Conclusions:
Maintain conatct with Troy, use the website to help us with the project charter. Contact Deid about Moodle.
Action items:
Person responsible:
Page 5 of 53
Deadline:
Project Meeting
Date: 24.1.11
Time: 15:00
Meeting called by:
Marla Weston
to 16:00
Type of meeting:
Weekly Progress
Attendees:
Marla Weston
William Heaton
Matt Donnolly
Jay Michael
Please bring:
----- Agenda Topics -----
Item 1: Year of Science awards
Time: 3:00
to 4:00
Discussion:
Surveying the students/teachers that took an Alice course at BBTC.
Talk to the teacher to garner couse feedback
Conclusions:
Listen to what the students say in terms of project requirements
What content worked for the instructor?
How will the server be set up?
Action items:
Person responsible:
Deadline:
Survey students
TEAM
25th Jan
Come up with questions to ask teacher.
Page 6 of 53
----- Agenda Topics -----
Item 2: Discussion of project reports
Time: 3:00
to 4:00
Discussion:
Need to get reports signed prior to Weds meeting.
Questions about the scope of the project charter
Conclusions:
Agile project, scope very flexible.
Action items:
Person responsible:
Deadline:
Send reports on Tuesday night.
TEAM
Begin
Begin working on a sample Tutorial.
immediately
Page 7 of 53
Project Meeting
Date: 31.1.11
Time: 15:00
Meeting called by:
Marla Weston
to 16:00
Type of meeting:
Weekly Progress
Attendees:
Marla Weston
William Heaton
Matt Donnolly
Jay Michael
Please bring:
----- Agenda Topics -----
Item 1: Progress
Time: 3:00
to 4:00
Discussion:
Conclusions:
Action items:
Person responsible:
Deadline:
Survey students
TEAM
25th Jan
Come up with questions to ask teacher.
Page 8 of 53
----- Agenda Topics -----
Item 2: Alice Workshop May 5th
Time: 3:00
to 4:00
Discussion:
Discussion of the workshop. 30-60 mins on Alice.
What happened in previous workshops, Marla and Troy’s experiences.
Action items:
Person responsible:
Deadline:
TEAM
Begin
immediately
----- Agenda Topics -----
Item 2: Curriculum
Time: 3:00
to 4:00
Discussion:
How would you combine the CST concepts with the Aboriginal Heritage
What would you include in the tutorials?
Potential issue with Windows 7 bugs in newer version sof Alice.
Action items:
Person responsible:
Deadline:
TEAM
Begin
immediately
Page 9 of 53
Meeting with Troy
Date: 7.2.11
Time: 10:30
Meeting called by:
to 13:30
William Heaton
Type of meeting:
Requirements gathering
Attendees:
Troy Verrin
William Heaton
Please bring:
----- Agenda Topics -----
Item 1: Course content
Time: 3:00
to 4:00
Discussion:
What to improve in the original content.
How to balance the focus of Aboriginal sorytelling with the progamming skills.
Conclusions:
Short presentations with a lot of activities.
Video tutorials that the kids and follow and copy.
Different levels of material for different abilities.
The project is progressing well, there are no issues to report.
Action items:
Us the information gathered to help propare the new course
content.
Page 10 of 53
Person responsible:
ALL
Deadline:
----- Agenda Topics -----
Item 2: Alice Workshop May 5th
Time: 3:00
to 4:00
Discussion:
Alice tips and tricks to make story telling easier.
Action items:
Person responsible:
Using poses, dummy items, modifying objects in paint, vehicles,
IsFirstClass, debugging.
Page 11 of 53
Deadline:
5/5/11
Project Meeting
Date: 14.2.11
Time: 15:00
Meeting called by:
Marla Weston
to 16:00
Type of meeting:
Weekly Progress
Attendees:
Marla Weston
William Heaton
Matt Donnolly
Jay Michael
Diane Biin
Please bring:
----- Agenda Topics -----
Item 1: BC Campus Proposal
Time: 3:00
to 4:00
Discussion:
Requirements of the project in relation to the objectives set out in the new grant.
Conclusions:
Need to configure moodle to have different roles and in different environments.
Action items:
Person responsible:
Deadline:
Look into the configurability of the moodle environment.
Matt
23rd Feb
Page 12 of 53
----- Agenda Topics -----
Item 2: Camtasi and 3GSTudio Max
Time: 3:00
to 4:00
Discussion:
Need to obtain keys from Mike
How we can use 3GMax to manipulate the 3d models in Alice
Action items:
Person responsible:
Marla will talk to Mike about keys.
Marka
Deadline:
----- Agenda Topics -----
Item 2: Curriculum and Language
Time: 3:00
to 4:00
Discussion:
Discussion of how to break down the curriculum into 3 levels; beginner, intermediate and advanced.
Matt repeated the discussion he had with Cora about how to improve the course material.
Talked about how best to incorporate language and stories into the curriculum.
Action items:
Person responsible:
Deadline:
Email T’sou-ke spirit festival to see if we can film dances.
Bill
19th Feb
Page 13 of 53
Project Meeting
Date: 21.2.11
Time: 15:00
Meeting called by:
to 16:00
Marla Weston
Type of meeting:
Weekly Progress
Attendees:
Marla Weston
Troy Verrin
Matt Donnelly
Jay Michael
Diane Biin
Please bring:
----- Agenda Topics -----
Item 1: Installing Moodle VM at school
Time: 3:00
to 4:00
Discussion:Implementing a machine with moodle having better capabilities then matts server at home.
Using linux for the OS in which the VM is installed on.
Weither or not we are putting it on the same VM as where the website is on.
Conclusions:Installing it on a VM at school
Action items:
Person responsible:
Create VM and install moodle
The Team
----- Agenda Topics -----
Page 14 of 53
Deadline:
Item 2: Creating a sample tutorial and putting it into
moodle
Time: 3:00
to 4:00
Discussion:installed xp in a vm with camtasia and alice to give us the ability to create a test tutorial.
Will be ceating gmail/youtube acounts for us to be able to export out camtasia videos and link to Moodle.
Conclusions: Working on a test tutorial and implementing it into moodle.
Action items:
Person responsible:
Work on test tutorial.
The Team
Deadline:
----- Agenda Topics -----
Item 2:Contacting and bringing in Suzzanne and Deid
Time: 3:00
to 4:00
Discussion: Utilizing Moodle and camtasia experts, contacting suzanne and deid.
Learning basic moodle functionality and camtasia.
Conclusions: Asking if Suzzanne and Deid will come into one of our Monday meetings.
Action items:
Person responsible:
Contact Suzzanne and Deid
Marla
Page 15 of 53
Deadline:
Weekly Status Report 1
Date:
January 19, 2011
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnolly
Activities accomplished last week:
Activity
We met with project Sponsor Marla Weston and Dianne Binn to
discuss the project scope and direction.
Member Name Time (hrs)
All
1x3,
We practiced the Alice software.
All
1x4, 1x1.5
1x3
We investigated the Moodle content management
system
All
1x1,1x3
Activities planed for next week:
Activity
Member Name Time (hrs)
All
3x3
We will further investigate the Moodle platform as a host for the
All
Ancestor resources.
We will attend an awards ceremony for high school students that have
used Alice. Interview the students and teachers to garner details in
All
relation to what teaching resources are required.
2x3
We will familiarize ourselves further with the Alice software.
3x2
Problems encounters:


Resolutions:


Other Notes:


Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Page 16 of 53
Weekly Status Report 2
Date:
January 19, 2011
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnolly
Activities accomplished last week:
Activity
We met with project Sponsor Marla Weston and Dianne Binn to
discuss the project scope and direction.
Member Name Time (hrs)
All
1x3,
We practiced the Alice software.
All
1x4, 1x1.5
1x3
We investigated the Moodle content management
system
All
1x1,1x3
Activities planed for next week:
Activity
Member Name Time (hrs)
All
3x3
We will further investigate the Moodle platform as a host for the
All
Ancestor resources.
We will attend an awards ceremony for high school students that have
used Alice. Interview the students and teachers to garner details in
All
relation to what teaching resources are required.
2x3
We will familiarize ourselves further with the Alice software.
3x2
Problems encounters:


Resolutions:


Other Notes:


Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Weekly Status Report 3
Page 17 of 53
Date:
January 26, 2011
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnally
Activities accomplished last week:
Activity
We met with Cora, the students and Troy to discuss ways to improve
the course content.
Member Name Time (hrs)
All
3x1,
We practiced the Alice software.
All
1x4, 1x4
1x3
We installed the Moodle content management system
Matt
1x3,
We completed the Project Charter
All
1x1, 1x1,
1x6
Activities planed for next week:
Activity
We will continue to familiarize ourselves further with the Alice
software.
We will further investigate the Moodle platform as a host for the
Ancestor resources.
We will write up some requirements garnered from the awards
ceremony.
Member Name Time (hrs)
Begin work on a sample tutorial if we have the software.
All
3x3
All
3x1
All
1x1
All
3x1
Problems encounters:
 Defining Scope/out of scope

Resolutions:
 The project is agile so the scope will be very flexible.
 More requirements were gathered from the meeting with students, and their teacher.
Other Notes:


Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Weekly Status Report 4
Date:
January 31, 2011
Page 18 of 53
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnolly
Activities accomplished last week:
Activity
We met with Cora, the students and Troy to discuss ways to improve
the course content.
Member Name Time (hrs)
All
3x1,
We practiced the Alice software.
All
1x4, 1x4
1x3
We installed the Moodle content management system
Matt
1x3,
We completed the Project Charter
All
1x1, 1x1,
1x6
Activities planed for next week:
Activity
We will continue to familiarize ourselves further with the Alice
software.
We will further investigate the Moodle platform as a host for the
Ancestor resources.
We will write up some requirements garnered from the awards
ceremony.
Member Name Time (hrs)
Begin work on a sample tutorial if we have the software.
All
3x3
All
3x1
All
1x1
All
3x1
Problems encounters:
 Defining Scope/out of scope

Resolutions:
 The project is agile so the scope will be very flexible.
 More requirements were gathered from the meeting with students, and their teacher.
Other Notes:


Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Weekly Status Report 5
Date:
February 2, 2011
Page 19 of 53
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnelly
Activities accomplished last week:
Activity
Contacted Troy and Cora to organize formal interviews for
requirements gathering.
Member Name Time (hrs)
All
3x0.25
We practiced the Alice software.
All
1x4, 1x4
1x3
We began configuring the Moodle content management
system.
Matt
1x3,
We conducted a presentation on the Project Charter
All
1x1, 1x1,
1x6
Activities planned for next week:
Activity
Member Name Time (hrs)
All
3x1
Meet as a team to share what has been learnt using Moodle and Alice.
All
Discuss requirements gathered from interviews.
3x1
We will write up some requirements garnered from the interviews.
All
1x1
Continue practice on Alice and Moodle.
All
3x3
Begin work on a sample tutorial if we have the software.
All
3x1
Meet with Cora and Troy for requirements gathering
Problems encounters:
 Waiting for confirmation of a meeting with Cora.
 Waiting on the tutorial software.
Resolutions:
 We will gather more requirements by having personal interviews with Cora and Troy.
Other Notes:
 Created online documents to track tasks and deadliness.
Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Weekly Status Report #6
Date:
February 9, 2011
Page 20 of 53
Project Name:
Ancestor Project
Submitted by (members):
Bill Heaton
Jason Michael
Matt Donnelly
Activities accomplished last week:
Activity
Member Name Time (hrs)
Met with Cora to discuss curriculum
Matt, Jason
1X2
Met with Troy for demonstration of Alice techniques
Bill
3
Met with Marla and Dianne and Troy to discuss progress
Matt, Jason,
Bill
1.5 x 3
Activities planed for next week:
Activity
Member Name Time (hrs)
Install and explore the use of Camtasia software
Matt
1
Continue learning to use Alice software
Matt, Jay, Bill
2x3
Work on Project Plan presentation
Matt, Jay, Bill
2x3
Problems encounters:
 Camtasia Software licensing is an issue. It can only be installed on one pc.
(Education license)

Cora was unable to use most of Troy`s curriculum due to students’ abilities.
Resolutions:


Other Notes:


Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Page 21 of 53
Weekly Status Report 7
Date:
February 16, 2011
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnelly
Activities accomplished last week:
Activity
Member Name Time (hrs)
Project Plan
Bill, Matt, Jay
1x3
Continue practice on Alice and Moodle.
Jay, Matt, Bill
2x2
Activities planned for next week:
Activity
Member Name Time (hrs)
Preparing for Project Plan Presentations
All
3x1
Continue practice on Alice and Moodle.
All
3x3
Problems encounters:
 Deciding how to allocate the keys amongst the teams.
Resolutions:
 Obtained keys for the use of Camtasia
 Outlined the initial phase of the development.
Other Notes:
Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Page 22 of 53
Weekly Status Report #9
Date:
March 02, 2011
Project Name:
Ancestor Project
Submitted by (members):
Matt Donnelly
Jason Michael
Bill Heaton
Activities accomplished last week:
Activity
Member Name Time (hrs)
Worked on SRS
Matt, Bill, Jay
Created YouTube Repository
Matt
1
Installed new version of Moodle onto VM provided by
Mike(IT Services)
Matt, Jay
2x1
Activities planed for next week:
Activity
Member Name Time (hrs)
Continue working on populating Moodle with Curriculum Matt, Bill, Jay
3x1
SRS Completion
Matt, Bill, Jay
Continue to learn Alice
Matt, Bill, Jay
3x1
Continue to learn Moodle
Matt, Bill, Jay
3x1
Problems encounters:
 Difficulties installing new version of Moodle. PHP Modules were needed.
 Camtasia had issues loading .swf files onto YouTube repository. Resolution issues
were encountered.
Resolutions:
 Researches lead us to finding which PHP modules to install.
 Manually uploaded tutorial demo to YouTube so it could be embedded into Moodle
curriculum page.
Other Notes:


Faculty Supervisor:
Marla Weston
Name
Initial
date
Initial
date
Instructor:
Name
Page 23 of 53
Weekly Status Report 10
Date:
March 9, 2011
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnelly
Activities accomplished last week:
Activity
Member Name Time (hrs)
SRS Document
Bill
1x3
Continue practice on Alice, Camtasia and Moodle.
Jay, Matt, Bill
3x1
Created YouTube channel.
Matt, Jay
2x0.5
Activities planned for next week:
Activity
Member Name Time (hrs)
SRS Document
All
3x5
Continue practice on Alice, Camtasia and Moodle.
All
3x1
Problems encounters:
 Installing Camtasia in a universally accessible place
Resolutions:
 File dropbox available on moodle and the size is configurable.
Other Notes:
Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Page 24 of 53
Weekly Status Report 11
Date:
March 16, 2011
Project Name:
Ancestor
Submitted by (members):
Jason Michael
William Heaton
Matt Donnelly
Activities accomplished last week:
Activity
Member Name Time (hrs)
SRS Document
Bill, Matt, Jay
3x3
Continue practice on Alice, Camtasia and Moodle.
Jay, Matt, Bill
3x1
Assign roles for comp299
Matt, Jay
3x0.25
Activities planned for next week:
Activity
Member Name Time (hrs)
SRS Document
All
3x5
Continue practice on Alice, Camtasia and Moodle.
All
3x1
Update introductory unit for clarification.
Bill
1x1
SRS Presentation
All
3x2
Put a VM onto one of the Camosun machines
Matt
1x1
Problems encounters:

Resolutions:
 Camtasia and Alice will be installed in 186 using a trial Camtasia license.
Other Notes:
Faculty Supervisor:
Name
Initial
date
Name
Initial
date
Instructor:
Page 25 of 53
Camosun College
Capstone Project
Ancestor Project
Project Charter
Author:
Creation Date:
Last Updated:
Version:
William Heaton, Jason Michael, Matt Donnally
January 25, 2011
January 26, 2011
1.0
Approvals:
Project Sponsor
Marla Weston
Dianne Biin
Signature
Date
Signature
Date
Signature
Date
Signature
Date
Signature
Date
Team
William Heaton
Jason Michael
Matt Donnolly
Faculty Supervisor
Marla Weston
February 8, 2016
Version 0.1
Page 26 of 53
Purpose of Document
This document defines the project in terms of objectives, scope, stakeholders and major deliverables. It is the venue
through which to seek project approval.
Table of Contents
Purpose of Document ................................................................................................................................ 27
Table of Contents ....................................................................................................................................... 27
Executive Summary.................................................................................................................................... 28
1.0
Project Purpose ....................................................................................................................... 29
2.0
Objectives ................................................................................................................................ 29
3.0
Stakeholders ............................................................................................................................ 29
4.0
Communications/Reporting Plan .......................................................................................... 30
5.0
Scope ........................................................................................................................................ 31
6.0
Major Deliverables .................................................................................................................. 32
7.0
Project Milestones .................................................................................................................. 32
8.0
Links and Dependencies ........................................................................................................ 32
9.0
Issues and Constraints .......................................................................................................... 33
10.0
Internal Resources Required ................................................................................................ 33
11.0
Reviews and Document Control ........................................................................................... 33
Page 27 of 53
Executive Summary
The goal of the Ancestor Project is to encourage Aboriginal youth to consider a future in information systems
technology (IST) by learning fundamental programming skills using the Alice software. The Alice software is a
visual tool that allows users to create stories and games that operate using object orientated programming
paradigm. Alice offers immediate graphical feedback and an easy ‘drag and drop’ interface that removes
many of the initial barriers of entry to programming such as syntax, compilers and documentation. The
project will also customize the environment by adding a variety of images (i.e. objects) that are important to
Aboriginal storytelling, thus enabling students to learn some of their cultural heritage in conjunction to
learning new IST skills.
The first phase of the project was completed in January 2011. In this initial phase, curriculum was developed
along with a sample story and game. A project website was also created. The curriculum was then
implemented in a test elective at the LÁU,WELNEW Tribal School starting in September 2010. This test
elective completed in mid January, 2011.
In the second phase, the goal is to build upon the resources and relationships established in the first phase.
Using feedback from the test elective at the LÁU,WELNEW Tribal School, this project will provide the required
resources deemed most necessary to help students and teachers learn the Alice software. Initially some Video
tutorials showcasing some of the fundamental programming concepts will be created. These will be added to
the project website. An online content management system (CMS) will be deployed to allow distributed
teachers to share resources and ideas as well as a standalone product for communities with limited internet
access. Given time, the project will also create more resources, such as stories, lesson plans and schemes of
work. Documentation will be provided for each of the resources to support teachers; however, the long term
goal is to use the CMS to create a network of support enabled by the teachers themselves.
The project is being sponsored by Dr. Marla Weston and Dianne Biin who will be working to grow the number
of schools engaging in the Ancestor project throughout this second phase’s timeline. Troy Verrin, one of the
project’s phase one team members, will also be involved in an advisory capacity. Schools participating at this
juncture include the LÁU,WELNEW Tribal School and discussions are underway with the Sooke school board
who are looking to join by September 2011 at the latest.
Page 28 of 53
1.0
Project Purpose
The purpose of the Ancestor project is to promote Computer Science skills in Aboriginal youth. The
Aboriginal communities are a proportionally underrepresented group in the Information Systems marketplace. The Ancestor project is using the Alice programming environment as a tool to help teach IST skills
in a culturally relevant manner by including stories and 3D models from their own history. It is hoped that
this will encourage students to pursue IST as a potential career. The project, which is now in its second
phase, will also provide a content management system for teachers using the Alice environment to be
able to share resources and ideas amongst themselves.
The first phase of the project created a website for the project (www.ancestorproject.org), along with a
number of stories in the Alice environment and a game also using Alice. Also during this phase, a
workshop highlighting the project and developed curricula was given at the S'tenistolw Conference (April
19 & 20, 2010). The intent of the S'tenistolw Conference "was to create an opportunity for Indigenous
instructors, faculty, administrators and other champions of Indigenous education to network and interact
- to share, learn and exchange info with one another with a view to creating opportunities for ongoing
communication." (http://camosun.ca/aboriginal/pdf_files/stenistolw-report.pdf)
The developed curricula was further tested in a pilot elective at the LÁU,WELNEW Tribal School. Although
the previous Capstone team's involvement officially ended in June 2010, Troy Verrin of that team
continued to act as a resource, and helped out at the school on several occasions. Troy remains a
valuable resource to both the project and the current team. The second phase of the project will build
upon these relationships as well as developing new ones. We will also create a standalone product for
those schools in more remote areas that have limited internet access. One of the core specifications for
this phase is to create video tutorials to help instructors and students learn about Alice. Given time we
will also develop more stories and teaching materials.
2.0
Objectives
The objectives of this 3 year project are to:




3.0
Use the Alice programming environment, populated with relevant cultural images and
sounds, to teach Aboriginal youth programming skills.
Create an up-to-date website to display examples of the students work and the Ancestor
projects current status.
Build upon the educational package year upon year to provide more material streamlined
content refined through feedback from participating schools.
Finalize the website and educational package in its final year, with the intention to promote
the program at the annual First Nations Education Steering Committee education conference.
Stakeholders
The following stakeholders’ (internal and external) interests must be considered throughout the project:
Stakeholder
Represented by
Interests, Expectations, Concerns
Camosun College
Dr. Marla Weston,
Dianne Biin
First Nations
Selection of teachers
To develop upon the work done by last year’s
Capstone team by providing new learning
material and a repository from which users can
share material.
To obtain new resources to help them teach the
Communitry
Development Team
4.0
who will use the
Alice teaching tool.
William Heaton,
Jason Michael,
Matt Donnolly
Alice programming language as well a further
students cultural knowledge.
To build upon the work already completed by
providing new, high-quality resources, while
learning new skills and techniques in project
development.
Communications/Reporting Plan
Faculty Supervisor
Form/Level of Detail of
Communication
Frequency/Dates
Originator
Distribution/Information
Flow
Comments
Meetings
Weekly
Dr. Marla
Weston
Verbal: Meetings to
discuss recent
developments, issues
and changes to scope.
email
As required
Dr. Marla
Weston/
Team
Email: to co-ordinate
any meeting/project
changes.
Form/Level of Detail of
Communication
Frequency/Dates
Originator
Distribution/Information
Flow
Comments
Meetings
As required
Project
manager
Verbal: to discuss any
project deliverables and
major developments.
To be organized as
required by the project
manager. The meetings
will become more
structured and regular
as the project develops.
Email
As required
Team
Project updates,
changes and meeting
information.
Deliverables will also be
exchanged for updating
and proofing using
email.
Form/Level of Detail of
Communication
Frequency/Dates
Originator
Distribution/Information
Flow
Comments
Meetings
Weekly
Dr. Marla
Weston
See comments
The client is also the
Faculty supervisor so the
roles will have a very
large crossover and as
such the
meetings/emails will
Project Team
Client
cover both areas of the
project.
Email
As required
Client/Team
See comments
Form/Level of Detail of
Communication
Frequency/Dates
Originator
Distribution/Information
Flow
Email
As required
Client/Team
and
Stakeholders
Emails to coordinate
meetings and other
project activities such
as workshops.
Exchanging resources
for critical analysis and
feedback
Meetings/Workshops
As required
Client/
Stakeholder
Face to face
interaction with a
variety of stakeholders,
including students,
instructors
Other Stakeholders
5.0
Comments
Used to gather
information and
feedback on how to best
proceed with the
project.
Scope
In Scope
The scope of the project includes:










Creating and maintaining a workbook containing all project correspondence between team
members and clients.
Finalizing a project charter.
Maintaining a project estimation plan, tracking time spent working on the project.
Produce a project plan.
Write the project system requirement specification document.
Review and select the content management system most appropriate for this project.
Create video tutorials to help students and instructors learn to program in Alice.
Develop preliminary training materials to be used during student workshops.
Provide IT support for instructors and students before and during project workshops.
Update the project website to reflect new work being completed.
Out of Scope
The following items are out of scope and provided here to help clarify the scope boundaries of the
project:

Creating advanced placement options for participants within British Columbia college and
university computer science departments.

Conducting a statistical analysis of survey results for workshops.

Presenting results to the provincial Aboriginal Youth Conference

Presenting results to the First Nations Education Steering Committee education conference.
6.0
Major Deliverables
The major deliverable products for this project are:
MAJOR
DELIVERABLE
Project Charter
Project Plan
SRS
Video Tutorials
Content Management
System
Update current
curriculum material
Update project
Website
7.0
DESCRIPTION
TARGET DATE
Statement of scope and
objectives.
Statement of how and when project
objectives are to be completed.
Analysis of the requirements of the
proposed system.
A selection of tutorials designed to help
students and instructors become familiar
with Alice.
A central repository online and stand alone
to provide teachers with a set of resources
to help them teach using Alice.
Streamline the current curriculum based on
feedback acquired from the initial test
group.
Add project deliverables and updated course
content to the Ancestorproject.org
website.
January 26, 2011
February 16, 2011
March 23, 2011
TBD
TBD
TBD
TBD
Project Milestones
The major milestones / targets / review points for the project are:
8.0
Milestone
Target Date
Initiation
Software Requirements Specification
Video Tutorials
Content Management System
Course content review and updates
January 5, 2011
March 23, 2011
TBD
TBD
TBD
Links and Dependencies
This project is dependent on the following:
 A number of proposals have been submitted applying for grant money to further develop the
project. Some of the software, scope and technologies available may be dependent on this.
 The Emily Carr University of Art and Design has been contacted and has agreed to produce some
3D models that we can incorporate into the Alice environment.
Projects and initiatives that depend on this project include:
 The LÁU,WELNEW Tribal School and other to be confirmed schools that will use the resources
produced in this phase of the project.
Success of this project is linked to the following:

The 3D models provided by the Emily Carr University of Art and Design.
Future work dependent on the completion of this project includes:

Further iterations of the Ancestor project development cycle are dependent on what we complete
in our phase.
9.0
Issues and Constraints
Issues and constraints that could impact project success include:
10.0

Obtaining the 3D models required for a flexible environment to tell Aboriginal stories.

Obtaining grant money to acquire software licenses.

Availability of the Ancestor project users for feedback and information.
Internal Resources Required
Estimated resource requirements include:
Resource Role
Project Sponsor
Project Manager
Project Faculty Adviser
Subject Matter Expert
User community
11.0
Dr. Marla Weston and Dianne Biin
William Heaton
Marla Weston
Troy Verrin (Alice), Deid Reimer (Moodle)
Aboriginal community in BC
Reviews and Document Control
Reviews
This document has been sent to the following for their review and comment.
Name
Position
Dr. Marla Weston
Steve Lang
Date
Project
Sponsor/Advisor
298 Instructor
Document Control
Date
Version
Change Reference
Reviewed by
26 January
2011
0.1
Original document
Dr. Marla Weston
Capstone Project
Ancestor Project
Project Plan
Author:
Creation Date:
Last Updated:
Version:
William Heaton, Jason Michael, Matt Donnelly
Thursday 9, 2011
Thursday 16, 2011
1.00
Approvals:
Project Sponsor
Dr Marla Weston
Dianne Binn
Signature
Date
Signature
Date
Signature
Date
Signature
Date
Signature
Date
Team
William Heaton
Jason Michael
Matt Donnelly
Faculty Supervisor
Dr Marla Weston
February 8, 2016
Version 1.0
Table of Contents
Table of Contents ....................................................................................................................................... 35
1.0
Project Purpose ............................................................................................................................... 36
2.0
Background ..................................................................................................................................... 36
3.0
Objectives ........................................................................................................................................ 37
4.0
Scope................................................................................................................................................ 37
4.1
In Scope ....................................................................................................................................... 37
4.2
Out of Scope ............................................................................................................................... 37
5.0
Major Deliverables .......................................................................................................................... 37
6.0
Stakeholders .................................................................................................................................... 38
7.0
Links and Dependencies ................................................................................................................ 38
8.0
Issues and Constraints .................................................................................................................. 39
9.0
Critical Success Factors ................................................................................................................. 39
10.0
Assumptions ................................................................................................................................ 39
11.0
Approach ...................................................................................................................................... 39
12.0
Project Development Documents ............................................................................................. 40
12.1
Project Management .............................................................................................................. 40
12.2
Deliverables ............................................................................................................................. 40
13.0
Milestones .................................................................................................................................... 40
14.0
Resource Requirements ............................................................................................................. 41
14.1
Internal Resources ................................................................................................................. 41
14.2
External Resources ................................................................................................................. 41
14.3
Special Committees ................................................................................................................ 41
15.0
Organizational Structure, Roles & Responsibilities ................................................................ 41
15.1
Project Organization Chart .................................................................................................... 41
15.2
Roles and Responsibilities of Stakeholders and Project Team ......................................... 42
16.0
Project Control ............................................................................................................................ 43
16.1
Project Integration Management ......................................................................................... 43
16.1.1
Project Co-Ordination......................................................................................................... 43
16.1.2
Change Management ......................................................................................................... 44
16.1.3 Configuration Management ............................................................................................... 44
16.1.4
Documentation Management ............................................................................................ 44
16.2
Scope Management ................................................................................................................ 45
16.3
Time Management.................................................................................................................. 45
16.4
Quality Management .............................................................................................................. 45
16.5
Human Resource Management ............................................................................................ 45
16.6
Communication Management ............................................................................................... 46
16.7
Contract Management ........................................................................................................... 46
16.8
Risk Management ................................................................................................................... 46
16.8.1
Risk Identification and Mitigation ..................................................................................... 46
16.8.2
Problem Determination and Resolution ........................................................................... 46
16.8.3
Issue Management ............................................................................................................. 46
17.0
Project Review and Completion Criteria .................................................................................. 47
18.0
Reviews and Document Control ............................................................................................... 47
Appendix A: Communications Plan Matrix ............................................................................................. 48
Appendix B: Risk Identification & Mitigation ........................................................................................ 49
Appendix C: Configuration Management .............................................................................................. 50
Appendix D: Workplan ............................................................................................................................ 51
Appendix E: Applicable Standards ......................................................................................................... 52
1.0
Project Purpose
The purpose of the Ancestor project is to promote Computer Science skills in Aboriginal youth. The Aboriginal
communities are a proportionally underrepresented group in the Information Systems market-place. The
Ancestor project is using the Alice programming environment as a tool to help teach IST skills in a culturally
relevant manner by including stories and 3D models from their own history. It is hoped that this will
encourage students to pursue IST as a potential career. The project, which is now in its second phase, will
also provide a content management system for teachers using the Alice environment to be able to share
resources and ideas amongst themselves. The first phase of the project created a website for the project
(www.ancestorproject.org), along with a number of stories in the Alice environment and a game also using
Alice. Also during this phase, a workshop highlighting the project and developed curricula was given at the
S'tenistolw Conference (April 19 & 20, 2010). The intent of the S'tenistolw Conference "was to create an
opportunity for Indigenous instructors, faculty, administrators and other champions of Indigenous education
to network and interact - to share, learn and exchange info with one another with a view to creating
opportunities for ongoing communication." (http://camosun.ca/aboriginal/pdf_files/stenistolw-report.pdf)
The developed curricula was further tested in a pilot elective at the LÁU,WELNEW Tribal School. Although the
previous Capstone team's involvement officially ended in June 2010, Troy Verrin of that team continued to
act as a resource, and helped out at the school on several occasions. Troy remains a valuable resource to
both the project and the current team. The second phase of the project will build upon these relationships as
well as developing new ones. We will also create a standalone product for those schools in more remote
areas that have limited internet access. One of the core specifications for this phase is to create video
tutorials to help instructors and students learn about Alice. Given time we will also develop more stories and
teaching materials.
2.0
Background
The business need of the Ancestor Project has come about due to two dilemmas facing Aboriginal youth in
today’s society. First, a disjunct between the transference and interest in cultural knowledge has been
documented. The project focuses on providing youth with culturally relevant tools to learn more about their
traditional history and language. Secondly, statistics have shown that Aboriginal youth are very
underrepresented in the field of Computer Science. The opportunity to provide an entry level, culturally
relevant, software programming course has become a reality using the University of Carnegie Mellon Hall
Alice 3d architecture.
The project will focus on creating workshop training material promoting interesting and fun programming
methods. Alice 3d provides an interactive, declarative interface to the world of software design, providing
students with an artistic non-structured way to learn programming methodologies and techniques. Aboriginal
youth will be invited to team led and organized workshops, where they will be instructed on the basics of
Object Oriented programming and 3d animation.
The project is expected to grow rapidly in interest over the second year, predominantly from the Saanich
Indian School Board. The mandate for the project is to expand the number of students and geographic
locations in each successive phase of the program.
It is expected that once the program is delivered in different Aboriginal communities across the province, it
could become of interest nationally once complete.
3.0
Objectives
The objectives of this 3 year project are to:
* Use the Alice programming environment, populated with relevant cultural images and sounds, to teach
Aboriginal youth programming skills.
* Create an up-to-date website to display examples of the students work and the Ancestor projects current
status.
* Build upon the educational package year upon year to provide more material streamlined content refined
through feedback from participating schools.
* Finalize the website and educational package in its final year, with the intention to promote the program at
the annual First Nations Education Steering Committee education conference.
4.0
Scope
4.1 In Scope
The scope of the project includes:










Creating and maintaining a workbook containing all project correspondence between team
members and clients.
Finalizing a project charter.
Maintaining a project estimation plan, tracking time spent working on the project.
Produce a project plan.
Write the project system requirement specification document.
Review and select the content management system most appropriate for this project.
Create video tutorials to help students and instructors learn to program in Alice.
Develop preliminary training materials to be used during student workshops.
Provide IT support for instructors and students before and during project workshops.
Update the project website to reflect new work being completed.
4.2 Out of Scope
The following items are out of scope and provided here to help clarify the scope boundaries of the
project:
5.0

Creating advanced placement options for participants within British Columbia College and
university computer science departments.

Conducting a statistical analysis of survey results for workshops.

Presenting results to the provincial Aboriginal Youth Conference

Presenting results to the First Nations Education Steering Committee education conference.
Major Deliverables
The major deliverable products for this project are:
MAJOR
DELIVERABLE
Project Charter
Project Plan
DESCRIPTION
Statement of scope and
objectives.
Statement of how and when project
objectives are to be completed.
TARGET DATE
January 26, 2011
February 16, 2011
SRS
Video Tutorials
Content Management
System
Update current
curriculum material
Update project
Website
6.0
Analysis of the requirements of the
proposed system.
A selection of tutorials designed to help
students and instructors become familiar
with Alice.
A central repository online and stand alone
to provide teachers with a set of resources
to help them teach using Alice.
Streamline the current curriculum based on
feedback acquired from the initial test
group.
Add project deliverables and updated course
content to the Ancestorproject.org
website.
March 23, 2011
TBD
TBD
TBD
TBD
Stakeholders
The following stakeholders’ (internal and external) interests must be considered throughout the project:
Stakeholder
7.0
Represented by
Camosun College
Dr. Marla Weston,
Dianne Biin
First Nations
Community
Selection of teachers
who will use the
Alice teaching tool.
Development Team
William Heaton,
Jason Michael,
Matt Donnelly
Interests, Expectations, Concerns
To develop upon the work done by last
year’s Capstone team by providing new
learning material and a repository from
which users can share material.
To obtain new resources to help them
teach the Alice programming language as
well a further students cultural
knowledge.
To build upon the work already completed
by providing new, high-quality resources,
while learning new skills and techniques
in project development.
Links and Dependencies
This project is dependent on the following:
 A number of proposals have been submitted applying for grant money to further develop the
project. Some of the software, scope and technologies available may be dependent on this.
 The Emily Carr University of Art and Design has been contacted and has agreed to produce some
3D models that we can incorporate into the Alice environment.
Projects and initiatives that depend on this project include:
 The LÁU,WELNEW Tribal School and other to be confirmed schools that will use the resources
produced in this phase of the project.
Success of this project is linked to the following:

The 3D models provided by the Emily Carr University of Art and Design.
Future work dependent on the completion of this project includes:
 Further iterations of the Ancestor project development cycle are dependent on what we complete
in our phase.
8.0
Issues and Constraints
Issues and constraints that could impact project success include:
9.0

Obtaining the 3D models required for a flexible environment to tell Aboriginal stories.

Obtaining grant money to acquire software licenses.

Availability of the Ancestor project users for feedback and information.
Critical Success Factors
Success of the seconds project phase will be determined as follows:



Modify curriculum
Make tutorial videos
Install CMS on standalone server
Overall project success is determined by:






10.0
Aboriginal youth show a statistically significant increase in wanting to learn more about computer
science.
Aboriginal youth show a statistically significant increase in their knowledge and interest of culture,
language and their natural environment.
Teachers and cultural knowledge keepers confirm both of the above.
The developed preliminary training materials can be used effectively by both teachers and youth.
There is an increased demand for the program.
Install newly developed curriculum into classrooms.
Assumptions
The following assumptions have been made for the project:

Create audio and video with Camtasia.

Embed tutorial videos into CMS.

Port modified curriculum into CMS.

Servers will be provided.

Cultural experts will be made available to answer development questions.

Network connectivity will be available in classrooms.
11.0
Approach
The approach of the project follows that of an agile development methodology. Each successive step of the
project will be reviewed with the client to confirm the direction of the project as a whole. As the project is a
draft pilot program, requirements and deliverables will change throughout the development life cycle. Some
deliverables of the design phase, such as the model gallery and workshop samples will be produced in
conjunctions with the SRS document of the Analysis phase. The major phases of the project are:

Analysis phase

12.0
o
o
o
o
o
Design
o
o
o
o
o
o
Project Charter
Project Plan
SRS Document
Practice Alice
Practice Moodle
Phase
Plan Content Management System(CSM)
Plan Curriculum development
Send CMS design for review
Send Curriculum plan for review
Finalize CMS design
Plan Video Tutorials
Project Development Documents
The Computer Science department in joint co-operation with the AECC will coordinate the project. The
deliverables of the project will be produced using Camosun College standards wherever possible. The
following lists the deliverable documents and identifies who will provide and approve them.
12.1 Project Management
DELIVERABLE
DOCUMENTS
Project Charter
Project Plan
SRS Document
PROVIDED BY:
Team
Team
Team
ACCEPTED BY:
Sponsor, Managers
Sponsor, Managers
Sponsor, Managers
12.2 Deliverables
DELIVERABLE
DOCUMENTS
Curriculum Design
Document
User Acceptance Test
Plan
Workshop training
materials
13.0
PROVIDED BY:
ACCEPTED BY:
Team
Sponsor, Managers
Team
Sponsor, Managers
Team
Sponsor, Managers
Milestones
The major milestones / targets / review points for the project are:
Milestone
Initiation
Software Requirements Specification
Video Tutorials
Content Management System
Course content review and updates
Target Date
January 5, 2011
March 23, 2011
TBD
TBD
TBD
14.0
Resource Requirements
The following table shows the estimated resource requirements for the project. This table summarizes
the resources documented in the workplan (see Appendix D). As the project progresses and the
workplan undergoes changes, this table may also change.
14.1 Internal Resources
Estimated internal resource requirements include:
Resource Role
Project Sponsor
Project Manager
Project Faculty Adviser
Subject Matter Expert
User community
Dr. Marla Weston and Dianne Biin
William Heaton
Dr. Marla Weston
Troy Verrin (Alice), Deid Reimer (Moodle)
Aboriginal community in BC
14.2 External Resources
Resources from outside the organization/unit include:
RESOURCE ROLE
Final Clients
NAME
Lau’welnew Tribal School
14.3 Special Committees
The following committees will be necessary for this project:
COMMITTEE
Steering
Committee
o
o
o
o
15.0
PURPOSE
Provides project direction
& guidance
Ensures stakeholder
interests
Discusses/resolves issues
Reviews/approves changes
& deliverables
MEMBERSHIP
Project Sponsor
Project
Managers
Organizational Structure, Roles & Responsibilities
15.1 Project Organization Chart
The following illustrates the reporting organization of the project.
TIMEFRAME
Weekly
Project Sponsor
Dianne Binn
Dr. Marla Weston
Project Managers
William Heaton
Development Team
William Heaton
Matt Donnelly
Jason Michael
15.2 Roles and Responsibilities of Stakeholders and Project Team
The following descriptions define the general roles and responsibilities of the resources to support this
project.
Role
Project Sponsor
Responsibilities













Project Steering Committee







Project Manager



Responsible for the project
Establishes business objectives
Confirms and approves project scope
Acquires and ensures sufficient funding is
obtained
Acquires and ensures sufficient program
resources
Promotes project
Monitors overall progress
Approves major deliverables
Ensures major objectives are being met
Reviews and approves Change Requests
Provides direction to project manager and client
manager
Resolves issues arising from the project
Responsible for final sign-off of the project.
Provides project direction and guidance
Ensures stakeholders interests are maintained
Discusses and resolves project issues
Reviews and resolves scope and change
requests
Ensures that all acceptance sign-off activities
are completed or returned within five business
days.
Reviews regular project status reports
Reviews and approves major project
deliverables
Chairs Steering Committee
Responsible for the delivery of the final product
and all interim deliverables as agreed in this
MPP and by subsequent change control.
Plans and controls all project activities.
Role
Responsibilities








Acceptance Test Team




16.0
Identifies and acquires resources.
Attends all Joint Application Design, project
status and review meetings as detailed in the
project plan.
Completes the assigned tasks at the scheduled
time as indicated in the project plan.
Manages issues, decisions, changes, and
problems to resolution.
Communicates status and project information to
sponsor, committees, and project stakeholders
on a regular basis as agreed.
Ensures all project tasks and deliverables
conform to Quality Management standards
where they exist and are appropriate to the
project.
Manages the project team including contributing
to performance processes.
Monitors contract(s) and ensures that
contracted deliverables meet the specifications
defined in Schedule A of the contract
Executes the User Acceptance Test Plan
Documents the results of the tests
Re-tests as required.
Identifies and participates in the resolution of
problems and issues
Project Control
This section describes how the project will be managed. It has been subdivided into the 9
Project Management “Knowledge Areas” defined by the Project Management Institute “Project
Management Body of Knowledge” (PMBOK).
Based on the Camosun College project management guidelines, where project triggers and
risks are assessed in order to determine the Level of Project Management (LOPM) required, the
project has been ranked low for project complexity.
16.1 Project Integration Management
16.1.1
Project Co-Ordination
The project will be coordinated using an Agile methodology, Camosun College standards
and guidelines, and general management principles. The project workplan (Appendix D),
developed in Microsoft Project, will be baselined and approved as part of this Project Plan.
The project plan will drive the project and will be monitored closely by the project
manager.
Prior to the start of each major project phase, the Project Plan and workplan will be
reviewed and revised, based on the information and experience of the previous phase and
any new information.
Progress will be reported to the Project Manager regularly as tasks are completed,
enabling the workplan to be kept up to date. Full project management meetings will be
held weekly on Monday to focus on milestones, action items, issues and concerns.
Team members will update a worksheet weekly to record how much time is spent on tasks
so the project manager can determine if efforts are being allocated appropriately.
16.1.2
Change Management
During the project, any stakeholder may request a change to the project definition (scope,
deliverables, schedule, cost) or to a previously approved project deliverable. A Change
Request will be created, analyzed for project effect, and reviewed by the Project
Management team.
All change requests will be logged into a workbook, an online document made available to
us by Google Documents, assessed for feasibility and impact, reviewed for approval, and a
resolution put in place. The resolution may result in changes to the workplan, project
plan, budget, contracts, or previous deliverables. The change process will be managed by
the project manager.
16.1.3
Configuration Management
The Software Configuration Plan in Appendix C describes how the software items will be
managed to ensure that they are always at a known state of development, review,
acceptance or use. This includes requirement specifications, technical design
specifications, tools, test data generators, procedures, management plans, systems and
user documentation.
The Apache Subversion change management tool will be used to support versioning and
configuration management.
16.1.4
Documentation Management
The Project Manager will manage the production of all documentation deliverables.
Camosun College standards will be used where standards exist.
The Project Manager will oversee the review and approval process for all documents.
Project Management documents (such as the Project Plan) will be reviewed and approved
according to the process established by the Project Team. Other documents will be
developed with the participation of users and therefore reviews will be an iterative process
throughout the creation period. Final reviews will thus be a confirmation, from both
project and user communities, of the documents’ contents.
Approved Project Management documents will be stored with the Project Manager and
available to the project team via the project repository. Deliverable documents will be
stored in the same manner.
At the completion of the project all documentation deliverables will be provided to
Camosun College and the Capstone instructor, Dr. Marla Weston, for long term storage
and maintenance.
16.2 Scope Management
The review and approval of the Project Plan and workplan will confirm the project scope. All
changes to the scope will be handled through change control.
16.3 Time Management
Planning is an iterative process involving all members of the project team. The major
planning for the project has been done in conjunction with this Project Plan, and is detailed in
the project workplan (Appendix D). Subsequent planning will be done with project team
members prior to the beginning of each phase of the project and for project change requests.
The workplan will be maintained by gathering progress information on a weekly basis from
our weekly development meetings and by updating the workplan accordingly. The schedule
will be reviewed with the client sponsor and faculty supervisor weekly during the same team
meetings.
Any changes to the schedule which affect major milestones or the final completion date will
go through change control, resulting in a new baselined version of the project workplan and
possibly a revision or new version of the Project Plan.
16.4 Quality Management
All project deliverables will be subject to a review and approval process and will be signed off
by the project sponsor and stakeholders with a vested interest in the particular deliverable.
Peer reviews will be held for business design and technical design documents, and codewalkthroughs for non-generated code.
In the interest of maintaining the schedule, tasks dependent on deliverables in the approval
process will be started. The risk associated with this method will be mitigated by including
the recipient of the deliverable in the review process.
A test strategy has been scheduled during the Implementation phase. This strategy will
include the development of test scenarios, test cases and a detailed test plan.
An acceptance test task is included in the workplan to enable Camosun College to test the
final product in a production-like environment prior to implementation. The initial
requirements for this acceptance test will be documented.
All system and application deliverables will be signed off prior to migration to production.
16.5 Human Resource Management
The resource requirements for this project are documented in Section 14 of this Project Plan
and in the project workplan (Appendix D).
All-team meetings will be scheduled periodically, which will provide a forum for project
management information exchange and team building.
16.6 Communication Management
The project team will produce a weekly status report, which will summarize major work
completed, in progress and due to start, and major issues and concerns.
The Project Manager will chair weekly status meetings with the project team to track progress
and discuss outstanding issues.
The project team will ensure that minutes are taken and distributed for every project meeting.
A matrix illustrating the Project Communication Plan is detailed in Appendix A.
16.7 Contract Management
None Applicable.
16.8 Risk Management
The project has considerable risk associated with it, and risk management will be a
primary focus of project management. The project workplan and budget have been
developed with some contingency to allow for both known risks and unknown risks.
16.8.1
Risk Identification and Mitigation
Refer to Appendix B for a Risk Analysis of the project. The project team will be continually
assessing and reviewing project risk to develop contingencies and to determine the best
courses of action. At the start of each project phase, the Risk Analysis will be repeated
and the project plans adjusted.
16.8.2
Problem Determination and Resolution
Any problems that may arise will be addressed by team members. I will be crucial to
resolve the issues before moving on to the next phase of the development as each phase
relies on the previous phase functionality. Problem management will be essential to the
success of the project
Most problems will be resolved within the project team and will not result in the creation
of an issue. However, for the short-duration project phases, some problems may escalate
into issues rapidly. Therefore, problem management will be very important and essential
to the resolution of issues and/or problems.
16.8.3
Issue Management
An issue is any concern that, if not resolved, can jeopardize the success of the project in
terms of schedule, cost or quality. Issues may be raised by any member of the project
team. All issues will be logged into our workbook. The project manager will review all
issues daily to ensure they are being dealt with in a timely manner. Outstanding issues
will be discussed [daily/weekly/ at each status meeting] and resolved as quickly as
possible. Major issues will be raised to the faculty supervisor and/or course instructor, and
may result in a change request to be initiated.
17.0
Project Review and Completion Criteria
The development team will conduct a brief post project evaluation review to assess the project
management of the project, to identify any “lessons learned” and improvements to
methodologies and procedures, and to identify potential enhancements to the final product.
The project will be deemed successful when all the objectives have been met.
The project will be deemed complete when:
18.0

Tutorial Videos have been created for each lesson plan

Updated curriculum has been delivered to classrooms.

Instructors have been trained on delivering curriculum to students.
Reviews and Document Control
Reviews
This document has been sent to the following for their review and comment.
Name
Dianne Biin
Dr. Marla Weston
Deid Reimer
Position
Project Sponsor
Project Manager
Faculty Advisor
Appendix A: Communications Plan Matrix
The following table shows the communications activities that will be performed during the
project.
Activities
Responsibility
Audience
1.
Project Stakeholder’s
weekly meeting.
Project Team
In
person
2.
Submit project
documentation for
review.
Project Team
Sponsor’s,
development
team
Sponsor and
advisor
3.
Submit project
Deliverables.
Project Team
Sponsor
Hard
Copy
4.
Development team
meetings
Development team
informal meetings.
Project Team
Development
team
Development
team
In
Person
Email
5.
Project Team
Method
Email
Suggested
timeframe
Every
Monday
Afternoon.
Prior to each
deliverable
date.
At the end of
Each project
Iteration.
Weekly.
As required.
Appendix B: Risk Identification & Mitigation
The following Risk Assessment has been developed by consensus amongst [ name groups
involved ], and reflects the risks as known at the date below. Risks change on a regular basis,
and this Risk Assessment will be repeated at periodic intervals throughout the project.
Date of Risk Assessment: February 16, 2011
Risk Event
or Assumption
1.
The 3D models
are not available on
time or not at all.
M
Likelihood
of
Occurrence
(L,M,H)
M
2.
Unable to embed
videos into
Moodle.
Project members
become
unavailable.
M
L
M
L
4.
Project Sponsors
become unavailable.
M
L
5.
Compatibility
issues with
different OS’s in
relation to Moodle
installation.
M
M
3.
Impact if Occurs
(L,M,H)
Mitigation
Plan
Use existing
models
available in
Alice library.
Include them in
a separate file
system.
Modify
deliverables
and divide
workload
amongst
remaining
members.
Have a well
defined plan
and maintain
contact via
email
throughout
development.
Use a VM
e.g. VM fusion.
Appendix C: Configuration Management
The Software Configuration Management Plan describes how the project will manage the
software items to ensure that they are always at a known state of development, review,
acceptance or use. The following table presents the configuration management standards for
the deliverables of this project. Where the configuration management has not been
completed, it will be addressed in a later stage of the life cycle.
Deliverable
Video Tutorials
Moodle
Website
Documentation for
CMS and tutorial
use.
Configuration Plan
Tutorials will be individually assigned on a weekly basis.
they will be peer-reviewed and then accepted by the
project sponsor.
Use an online repository (Apache subversion) to update
changes to the configuration. Update team members in
weekly scrum meetings.
Use an online repository (Apache subversion) to update
changes to the website. Update team members in weekly
scrum meetings.
Use an online repository (Apache subversion) to update
changes to the documentation. Update team members in
weekly scrum meetings.
Appendix D: Workplan
Appendix E: Applicable Standards
The following table identifies the applicable standards that must be followed and met
through the development of the project deliverables.
Document
Version
Published Date
NSERC Project
Proposal
B.C Campus
Proposal
1.0
December 12, 2009
1.0
December 20, 2010