MIS3535
On Track / At Risk
Work Completed:
Task Name Date Completed
1.
Project Schedule
2.
Problem Statement
3.
Project Charter
09.10.2014
09.10.2014
09.10.2014
4.
Work Breakdown Structure 09.10.2014
5.
Interview #1 Questions
6.
Risk Management Plan
09.11.2014
09.17.2014
7.
Communications Plan
8.
Quality Management Plan
9.
Change Management Plan
10.
Interview #2 Questions
11.
Scope Document
12.
Interview Questions #3
13.
Project Charter
09.17.2014
09.17.2014
09.17.2014
09.23.2014
09.24.2014
10.06.2014
10.08.2014
Summary Notes
Shows all tasks and resources assigned
Defines the problem to be solved
States that the project exists and has authorization from the PMs to begin work
Organizes the team’s work into manageable sections
Questions were very broad
Identifies risks and how they will be dealt with
Defines communication goals and strategies
Documents the information required to
effectively manage project quality
Tracks any changes made to the project
Questions were more specific
BAs combined individual scopes
Questions were much better
Statement of scope, objectives, and participants in the project
1

MIS3535
14.
Scope Revision
15.
List of Stakeholders
16.
Organization Chart
17.
RACI Chart
18.
Revised Budget
19.
Critical Path
20.
Prototype #1
21.
Use Case
22.
Prototype #2
23.
Persona/Story
24.
Revised RM Plan
25.
Business Rules
26.
Prototype #3
27.
Data Schema
Work in Progress:
Task Name
1.
Prototype #4
2.
Presentation
10.08.2014
10.13.2014
10.13.2014
10.13.2014
10.22.2014
10.29.2014
10.29.2014
10.29.2014
11.05.2014
11.05.2014
11.12.2014
11.12.2014
11.12.2014
11.12.2014
Planned End Date Resources Assigned
11.19.2014
12.03.2014
All BAs
All BAs
Work Schedule to begin:
Task Name Planned Start Date
1.
Revised Change Mgmt. Plan 11.17.2014
2.
Revised Comm. Mgmt. Plan 11.17.2014
3.
Prototype #5 11.19.2014
Revised scope based on professor’s comments and critique.
Lists all of the stakeholders & their roles
Diagram showing structure of team and relationships & links between members
Shows who is Responsible, Accountable,
Consulted, and/or Informed for tasks
An updated version of the budget; still needs to be implemented into Project
Integrated project into MS Project, used to determine critical path
First draft of the Justinmind; focused on front-end rather than back-end
Defines how users can use the prototype
Some front-end changes as well as working on making it functional
Layout of what the presentation will be like, and a persona to have a character in mind for the presentation
The plan is now 1 page and meets all of the requirements
Specifies all of the rules that must be followed for the project
The prototype’s design looks great.
They are still working on the functional aspects and making sure that it meets and professor’s requirements and business rules.
States all of the data masters and attributes for each of them within the prototype.
2

MIS3535
Descriptions
1.
None; we are in good shape
Actions
Description
1.
Staying on schedule
Actions
Specify where the BAs should be at the end of each week. The
PMs know how long each task should take.
Meetings that have taken place:
Description
1.
Kickoff Meeting #1
2.
Kickoff Meeting #2
3.
Weekly Meeting
4.
Weekly Meeting
5.
Weekly Meeting
6.
Weekly Meeting
7.
Weekly Meeting
8.
Justinmind Help
9.
Weekly Meeting
10.
Weekly Meeting
11.
Weekly Meeting
Date / Time Attendees
09.09.2014 @ 4pm Sandi, Melissa, Mike, & Trang
09.10.2014 @ 11am Arren, John, Melissa, Mike, & Tyler
09.26.2014 @ 4pm All PMs and BAs
10.03.2014 @ 4pm All PMs and BAs
10.10.2014 @ 4pm All PMs and BAs
10.20.2014 @ 4pm Arren, Evan, John, Stephanie, & all BAs
10.24.2014 @ 4pm All PMs and BAs
10.27.2014 @ 11am John, Arren, & all BAs
10.31.2014 @ 4pm All PMs and BAs
11.07.2014 @ 4pm All PMs and BAs, except Tyler
11.14.2014 @ 4pm PMs: John, Evan, Stephanie, Melissa;
BAs: Trang, Michael
Planned Meetings:
Description
1.
Weekly Meeting
2.
Weekly Meeting
3.
Weekly Meeting
Date / Time Attendees
11.21.2014 @ 4pm All PMs and BAs
11.28.2014 @ 4pm All PMs and BAs
12.05.2014 @ 4pm All PMs and BAs
3