MIS3535
Progress Report
Project Team #: Flanagan 2 – Doyle 3
Team Members: PMs: Stephanie Kilroy, Arren Soroko, Sandra Brown, John
Illuminati, Evan Bedor, Melissa Aguilar-Ramirez; BAs: Tyler DiBetta, Trang Nguyen,
Michael Paszkiewicz
Reporting Period From: 10.18.2014
Overall Project Status:
To: 10.24.2014
On Track / At Risk
Deliverables:
Work Completed:
Task Name
Date Completed
Summary Notes
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
09.17.2014
8. Quality Management Plan
09.17.2014
9.
10.
11.
12.
13.
09.17.2014
09.23.2014
09.24.2014
10.06.2014
10.08.2014
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
Change Management Plan
Interview #2 Questions
Scope Document
Interview Questions #3
Project Charter
1
MIS3535
14. Scope Revision
10.08.2014
15. List of Stakeholders
16. Organization Chart
10.13.2014
10.13.2014
17. RACI Chart
10.13.2014
18. Revised Budget
10.22.2014
19. Critical Path
10.29.2014
20. Prototype #1
10.29.2014
21. Use Case
10.29.2014
Work in Progress:
Task Name
1. Prototype #2
2. Data Schema
1.
2.
3.
4.
5.
6.
7.
8.
9.
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
Planned End Date
Resources Assigned
11.05.2014
11.05.2014
All BAs
All BAs
Work Schedule to begin:
Task Name
Planned Start Date
Prototype #3
Business Rules
Revised Risk Mgmt. Plan
Prototype #4
Presentation
Revised Change Mgmt. Plan
Revised Comm. Mgmt. Plan
Prototype #5
Final Presentation
11.05.2014
11.05.2014
11.10.2014
11.12.2014
11.12.2014
11.17.2014
11.17.2014
11.19.2014
11.19.2014
Project Issues
Descriptions
Actions
1. BAs still learning Justinmind
Provide continued assistance on extra credits prototype designs
2. Lack of MS Project experience Spend more time learning Project and how to utilize it with our
project
Project Risks:
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.
2
MIS3535
Meetings
1.
2.
3.
4.
5.
6.
7.
8.
9.
1.
2.
3.
4.
5.
Meetings that have taken place:
Description
Date / Time
Attendees
Kickoff Meeting #1
Kickoff Meeting #2
Weekly Meeting
Weekly Meeting
Weekly Meeting
Weekly Meeting
Weekly Meeting
Justinmind Help
Weekly Meeting
09.09.2014 @ 4pm
09.10.2014 @ 11am
09.26.2014 @ 4pm
10.03.2014 @ 4pm
10.10.2014 @ 4pm
10.20.2014 @ 4pm
10.24.2014 @ 4pm
10.27.2014 @ 11am
10.31.2014 @ 4pm
Sandi, Melissa, Mike, & Trang
Arren, John, Melissa, Mike, & Tyler
All PMs and BAs
All PMs and BAs
All PMs and BAs
Arren, Evan, John, Stephanie, & all BAs
All PMs and BAs
John, Arren, & all BAs
All PMs and BAs
Planned Meetings:
Description
Date / Time
Attendees
Weekly Meeting
Weekly Meeting
Weekly Meeting
Weekly Meeting
Weekly Meeting
11.07.2014 @ 4pm
11.14.2014 @ 4pm
11.21.2014 @ 4pm
11.28.2014 @ 4pm
12.05.2014 @ 4pm
All PMs and BAs
All PMs and BAs
All PMs and BAs
All PMs and BAs
All PMs and BAs
3