1. Class 5 – Planning IT Projects
Review SDLC
Triple Constraint
Iterative Planning
Project Life Cycle for MIS 374
Major Milestone Summaries
Network Diagrams
Gantt Charts
Iterative Planning with MS Project:
Gantt charts
Building a Project Plan exercise
AsIs verus ToBe
Get new environment template
Solution is up to you 1

2. * common acronym: SDLC: System Development Life Cycle
MIS 374 Project Life Cycle *
Final
Construction
Phase(s)
Inception
Phase(s)
This project life cycle is the required model for planning assignments that are part of Group Project 2 and the Client Project.
* common acronym: SDLC: System Development Life Cycle 2

3. Iterative phases to build functionality Prepare system for release
Project Life Cycle
N number of
Construction
Phases
Inception
Phase(s)
Establish Team and Roles
Define scope
Plan project
Prepare development environment
Iterative phases to build functionality
Prepare system for release 3

4. Defining Scope Establish Team and Roles Define scope Plan project
Inception
Phase(s)
Final
Construction
Phase(s)
Stakeholder Roles & Responsibilities Table
Software/hardware Environments
Root Cause Analysis
Process Modeling & Overview Graphics
Organizational Impact Analysis
Functional & Non-Functional Requirements
Risk Management
Return-on-Investment (ROI) Analysis
Web Flow Diagrams
Evaluation Tables for System Alternatives
Establish Team and Roles
Define scope
Plan project
Prepare development environment 4

5. Planning IT Projects Determine phases Milestone Summary Table
Inception
Phase(s)
Final
Construction
Phase(s)
Establish Team and Roles
Define scope
Plan project
Prepare development environment
Determine phases
Milestone Summary Table
Network Diagram
Gantt Chart 5

6. Preparing Development Environment
Inception
Phase(s)
Final
Construction
Phase(s)
Establish Team and Roles
Define scope
Plan project
Prepare development environment
Design Database & Information Architecture
Determine Production Software/Hardware Environments
Determine Development Environment
Set up Development Environment 6

7. Let’s review a critical concept
MIS 374 Project Life Cycle
Final
Construction
Phase(s)
Inception
Phase(s)
Middle tasks: build functionality
Wrap Up
Early tasks
Let’s review a critical concept 7

8. Someone explain the triple constraint (Very important lesson in PM)
Scope
Project Management
Triple Constraint
Tradeoff
Tradeoff
Resources
Money
People
Equipment
Schedule (Time)
Tradeoff ?

9. Hypothetical You could decrease scope of project
We’re implementing SAP at your company. The deadline is 2 months away and we’re behind schedule. We can’t work overtime and we can’t move deadline back. What can you do?
You could decrease scope of project
You’re building a website that will manage sales force. Currently we have a set scope and can’t go live without 100% of functionality. We have no more $$$ to hire more people. What can you do?
You could push deadline back

10. Example: Two 40 hour reports due by end of week
Decrease scope?
Push back deadline?
Increase resources?
We’re late!! What to do?

11. Manager Reports & Admin
Class Day 2, 8/29/2011
Return to the K project
Customer functions
Employee functions
Manager Reports & Admin 11

12. Network Diagram for K Project
Admin
Module
Employee Module
Managerial Reports
Customer Module
Phase 2 –
Phase 1 –
Phase 3 –
Phase 6 –
Inception Phase
Final
Construction
Go Live
Phase 4 –
All 4 team members meet w/ client for defining scope, planning, etc
IMPORTANT WORDING:
Deliver quick wins
Deliver often
Phase 5 –
Team members split up and focus on different functional areas

13. MIS 374 Planning Requirement
Gantt charts show entire Life Cycle

14. Network Diagram for Penguin Airlines
Admin
Module
Employee Module
Manager Reports
Customer Module
Phase 2 –
Phase 1 –
Phase 3 –
Phase 6 –
Inception Phase
Final
Construction
Phase 4 –
Phase 5 –

15. Excel example for ASTA Planning on Resources web page, Planning Block

16. Planning Techniques Exercise
Start
Finish

17. Planning Techniques Exercise
Collapsed Phases

18. Network Diagram of collapsed phases
Planning Techniques Exercise
Network Diagram of collapsed phases
Turn in the finished network diagram before next class

19. Exercise 6 – due before next class
Print a network diagram version of your in-class work today on one page.
Your diagram should be “collapsed” so that only your phases are on your diagram.
Your phases should all be connected by arrows that show dependencies.
Your phases (task boxes) should be readable. 19

20. Reminders: Client Bidding is coming up!
Friday at noon (on Clint’s watch) bidding starts
Be ready to go and submit as soon as bidding opens
NOTE: Only bid once so you don’t reset timestamp
We’ll notify you of client choices by end of day Friday
Client Meet & Greet is on Monday
No real client “work” will happen next week so you can focus on GP2
Please be there at 6:30pm in GSB 2.120
Strongly encouraged, not required. At least get one member there.
Contact client beforehand to ensure they’re coming 20

21. Client Project page

22. Exercise 6 - Planning exercise
1. Define Scope from Top-Down
Phases first
Then ADCR Loops in EACH phase
Then tasks under each loop
2. Then Set Durations per task
3. Assign who – (will do this in GP2 and CP)
4. Dependencies (We want to see parallel work and multiple releases)
5. Collapse all before creating Network Diagram
6. Careful to avoid ANALYSIS PARALYSIS
When this happens, we are over complicating things
So…how does this compare to Agile? 22