Project Management

1
Project Management

• CS2335
• Fall 2005

2
Agenda

• Lab Friday, Lab 3 continued, use for team
  meetings and coordination, notify me or TAs of
  any problems
• Email (please use gt account and cs2335 in
  headers!
• Where are we?
• Project Management Lecture

3
Why do Planning?

• Well-planned projects sometimes fail, Poorly
  planned projects usually fail
• Tells the team what has to be done, ensure
  work-load leveling
• Builds a shared understanding of project
• Builds shared commitment to project (if team has
  a say in preparation)

4
(No Transcript)
5
Project Management

• Meeting Management
• Decision Making
• Scheduling
• Estimation

6
Meeting Management

• Have an agenda (Topic Time Goal)
• Start/Stop on time
• Make decisions
• Have a strawman
• Keep on topic
• Have recorder and timekeeper
• Handle dysfunctional behavior

7
Sample Agenda
Review Previous Decisions 5 minutes
Analyze Requirements 15 minutes
Create WBS 20 minutes
Summarize Decisions 5 minutes
8
Making Decisions 9 Step Plan

• Define Problem
• Decide on method of attack
• Generate alternatives
• Test alternatives for reality
• Choose alternative
• Plan for action
• Implement plan
• Evaluate effectiveness
• Determine next steps

9
Scheduling

• Realistic Schedule
• Overly Optimistic Schedules
• Impossible Schedules

Completion ?
Schedule (Time)
10
Techniques

• Forward Plan (Earliest Finish)
• Backwards Plan (Latest Start)

Making your schedule
What do we have to do?
What has to be done first?
How long does it take?
How will we monitor our progress?
11
Determining Tasks (Activities)
Work Breakdown Structure (WBS) Top-Down
avoid design to organization
QuoteService
1. Preparation
2. Design
3. Implementation
4. Test
1.1 Read Lab
2.2 Protocol
2.1 Class ID
4.2 UT
4.1 Plan
4.3 IT
3.1 Code Modules
3.2 Create Ant
4.2.1 Junit
12
Determine Milestones

• Consume no resources
• Phrased as yes/no question
• Met or not met
• Track progress
• One per week

Milestone has a date and a goal. i.e. M1 Monday
6 June Client Connects to Server.
13
Determine Dependencies (Ordering of Tasks)
3.2
2.2
What has to be done first? What cant be done
till something else is complete? Can we arrange
so everyone is working all the time?
14
Determine Durations of tasks
3.2
1800 Fri
0900 Fri
2.2
SWAG (Scientific Wild Guess) sometimes based on
experience
PERT/CPM
15
Schedule

• Schedules Tasks Dependencies Milestones
  Resources
• What is the sequence we are doing things?
• Who is responsible for each thing?
• What checkpoints do we have to detect when things
  are going bad?
• Is workload level.

16
Representing Schedule

• Activity Network (PERT/CPM)
• Gantt Chart

3
4
5
tasks
1
2
T1. Bob Do basic class diagram for main app
Sally Screen UI drawings Stan Design
Text Protocol Exit Design approved by
team T2 Bob Code basic Server UI and connection
management services.
Exit Server starts/stops correctly,
login, register, logout work.
T1 Design M1 Design Done T2 Code Server T3
Code Client T4 Code Protocol
17
Project Management for Labs

• First Lab
• Team meets and analyzes Lab Description
• Before leaving lab show your TA
• Team member names, mail ids
• Team name
• Preliminary WBS (Doesnt have to be formal)
• Preliminary Design Ideas
• CVS Plan
• Date of next meeting

mandatory items
18
Project Management for Labs

• Second Lab (for multi-week labs)
• Before Leaving lab show TA
• Revised WBS
• Task Progress (Person-Hours Worked)
• Current Design
• Estimate of of code completed
• Problems/Issues
• ID design components that are not started

19
Iterative Development

• Divide the project into pieces
• Get each piece working
• Always have a demo-able app
• Write drivers to show classes work
• Daily Meeting
• What did you do yesterday?
• What are you planning to do today?
• What is stopping you from moving on?

20
Bobs Iterative Lab 3

• Design, draw ui screens, basic class structure,
  protocol
• ServerUI
• Server start, accept connections, start thread,
  stop
• User login, register, persist user classes
• Client UI
• Client login, register
• Client quote create, persist, display

21
Next Time

• Start Design/UML section