| Tasklist | ||||
|---|---|---|---|---|
| ||||
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name|| | |
...
T |
...
|M |
...
|F |
...
|1299905435128 |
...
|1343675967500 |
...
|pshepp@mit.edu |
...
|Program sponsor identified? |
...
F
...
M
...
F
...
1299906630908
...
| |T|M|F|1299906630908|1360783403215|pshepp@mit.edu |
...
|Key Stakeholders identified/stakeholder analysis completed? |
...
| |F |
...
|M |
...
|F |
...
1299905635800
...
...
mccollin@mit.edu
...
Have features in scope been identified?
...
F
...
M
...
F
...
1299905650502
...
...
mccollin@mit.edu
...
Have features 'out of scope' been identified?
...
T
...
M
...
F
...
1299905545826
...
1343675998525
...
mccollin@mit.edu
...
Project Steering Committee members identified, if applicable?
...
F
...
M
...
F
...
1299905507370
...
...
mccollin@mit.edu
...
Define project goals and objectives
...
F
...
M
...
F
...
1299905687953
...
...
mccollin@mit.edu
...
Have project success criteria been identified?
...
F
...
M
...
F
...
1299905738068
...
...
mccollin@mit.edu
...
Have risks been identified?
...
F
...
M
...
F
...
1299905772830
...
...
mccollin@mit.edu
...
Determine if there any conflicts with existing projects
...
F
...
M
...
F
...
1321553069340
...
...
mccollin@mit.edu
...
Are there any compliance issues to be considered?
...
F
...
M
...
F
...
1321553101467
...
...
mccollin@mit.edu
...
Are there any audit (internal or external) findings that should be addressed by the project?
...
F
...
M
...
F
...
1299906058399
...
...
mccollin@mit.edu
...
Will the existing technical infrastructure support this project?
...
F
...
M
...
F
...
1299905966288
...
...
mccollin@mit.edu
...
Has scope statement been written?
...
F
...
M
...
F
...
1299906261293
...
...
mccollin@mit.edu
...
Has project approach been determined?
...
F
...
M
...
F
...
1299905877071
...
...
mccollin@mit.edu
...
Has project been added to RT queue?
...
T
...
M
...
F
...
1299906424788
...
1343676032375
...
mccollin@mit.edu
...
Have resource requests been made to functional managers
...
T
...
M
...
F
...
1299906396804
...
1343676045333
...
mccollin@mit.edu
...
Has preliminary budget been reviewed by finance
...
F
...
M
...
F
...
1299906880251
...
...
mccollin@mit.edu
...
Has preliminary monthly forecast been submitted to finance
...
F
...
M
...
F
...
1299907528828
...
...
mccollin@mit.edu
...
Has preliminary project schedule been developed?
...
T
...
M
...
F
...
1299905863246
...
1343676058641
...
mccollin@mit.edu
...
Has project wiki been created?
...
F
...
M
...
F
...
1299905927841
...
...
mccollin@mit.edu
...
Have project processes been documented
...
F
...
M
...
F
...
1319877694731
...
...
mccollin@mit.edu
...
Have project processes been communicated to the team?
...
F
...
M
...
F
...
1299905757330
...
...
mccollin@mit.edu
...
Document risk and escalation procedure
...
F
...
M
...
F
...
1345733147111
...
...
mccollin@mit.edu
...
Research-Scope: audit file; requires full file from MITSIS, adds 4-8 weeks to project schedule
...
F
...
M
...
F
...
1345733175290
...
...
mccollin@mit.edu
...
Research - Scope: EECS file of new appts (impact to schedule unknown, analysis needed)
...
F
...
M
...
F
...
1345733223017
...
...
mccollin@mit.edu
...
Research-Scope:Improvements to Phase I functionality
...
F
...
M
...
F
...
1345733384038
...
...
mccollin@mit.edu
...
Schedule: Vacations/time off through next May
...
F
...
M
...
F
...
1345733543062
...
...
mccollin@mit.edu
...
- grad admins, # grad students
...
F
...
M
...
F
...
1345735539801
...
...
mccollin@mit.edu
...
|1299905635800| |@mit.edu|Have features in scope been identified?|
|F|M|F|1299905650502| |@mit.edu|Have features 'out of scope' been identified?|
|T|M|F|1299905545826|1343675998525|pshepp@mit.edu|Project Steering Committee members identified, if applicable?|
|F|M|F|1299905507370| |@mit.edu|Define projects, goals and objectives|
|T|M|F|1299905687953|1360783426933|pshepp@mit.edu|Have program success criteria been identified?|
|T|M|F|1299905738068|1360783428569|pshepp@mit.edu|Have risks been identified?|
|F|M|F|1299905772830| |@mit.edu|Determine if there any conflicts with existing projects|
|F|M|F|1321553069340| |@mit.edu|Are there any compliance issues to be considered?|
|T|M|F|1321553101467|1360783437402|pshepp@mit.edu|Are there any audit (internal or external) findings that should be addressed by the program?|
|T|M|F|1299906058399|1360783439364|pshepp@mit.edu|Will the existing technical infrastructure support this program?|
|T|M|F|1299905966288|1360783441020|pshepp@mit.edu|Has scope statement been written?|
|T|M|F|1299906261293|1360783442819|pshepp@mit.edu|Has program approach been determined?|
|T|M|F|1299905877071|1360783446886|pshepp@mit.edu|Does program require an RT queue?|
|F|M|F|1299906424788| |pshepp@mit.edu|Have resource requests been made to functional managers|
|T|M|F|1299906396804|1360783452909|pshepp@mit.edu|Has preliminary budget been reviewed by finance|
|T|M|F|1299907528828|1360783458719|pshepp@mit.edu|Has preliminary project schedule been developed?|
|T|M|F|1299905863246|1343676058641|@mit.edu|Has project wiki been created?|
|T|M|F|1299905927841|1360783465870|pshepp@mit.edu|Have program processes been documented|
|F|M|F|1319877694731| |@mit.edu|Have progrm processes been communicated to the team?|
|F|M|F|1299905757330| |@mit.edu|Document risk and escalation procedure|
|