Post on 13-Jan-2016
transcript
1 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Management for the MX generation
Shlomy Gantz
CFUN-02
2 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Buzzwords
• Process
• Requirements
• Teamwork
• Consensus
• “On-time, On Budget”
• Methodology
• Empower, Synergy, etc…
3 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Process”
4 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords - “Process”
5 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords - “Process”
• 4 Step, 5 Step, 12 Step…
• Who designed your process?
• Do you follow that process?
• Do you? Really?
• Do you update your process?
• How complex is your process?
• How abstract is your process?
6 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Requirements”
7 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords – “Requirements”
“I’ll need you to review these
300 use cases by Monday”
8 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Horror Story” #1
• Large airline industry project
• Thousands of documents
• 200 Consultants
• No consistensy
• No clear vision
• Project already late
• Too many project managers
9 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Horror Story” #1
• Re-State Goal
• New Document Templates and Management
• Buzzword free architecture
• Simple, Achievable Milestones
10 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords – “Requirements”
• Do you have enough requirements before you start coding?
• Do you, really?
• Can you have too much of it?
• Are they consistent?
• Can your requirements change?
• Are they simple to understand?
11 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Project Mangers”
12 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords – Project Managers
• Project Managers are overrated
• Project Leadership is needed instead of project management
13 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“on time and on budget”
14 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords – “on time and on budget…”
• Nearly a third of IT projects
were CANCELED before
they could be completed.
• Over half of the projects cost
almost TWICE as much as
their original approved budget
15 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Teamwork”
16 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords – “Teamwork”
• Hierarchies can inhibit communication
• One Good programmer is worth 10 mediocre
17 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Consensus”
18 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Buzzwords – “Consensus”
• Too much time and energy spent on consensus
• Great tool for Avoiding Accountability
• Promotes management by committee, slows development
19 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Famous first words”
20 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Famous first words
21 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Famous first words
22 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Famous first words
23 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Famous first words
24 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Famous first words
25 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Famous first words
26 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Reasons for Failure
• In software, past performance
is your best indicator of
future performance
• “Project success is determined
in the first month”
27 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Reasons for Failure
• Lack of clear vision
• Lack of communication
• Lack of flexibility
• Lack of creativity
28 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Success Factors
1. User Involvement……………………..…….202. Executive Management Support………...….153. Clear Statement of Requirements………..….154. Proper Planning ……………………….……10 5. Realistic Expectations …………….….…….10 6. Smaller Project Milestones ………….……..10 7. Competent Staff …………………………….5 8. Ownership…………………………………. .59. Clear Vision & Objectives ………………….5 10. Hard-Working, Focused Staff……………. .5
29 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Horror” Story #2
• “Instant” company 0-60 employees
in one month
• Extremely Short timeframe
• Not enough developers
• No planning or Vision
• Constant Scope creep
30 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
“Horror” Story #2
• Stop• Force everyone think the product does do,and
write it down.• Owner and President given a multiple choice
questionnaire based on response.• Mini-plans, small milestones/tasks – complete a
feature• Momentum – team happier, more productive• Project gets done
31 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Management – The problem
• Phase Isolation – “Plan, then do”
• Requirements done once and set in stone
• Requirements are not simple to understand
• Implementation is done in Isolation
32 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Management – The Solution ?
• RUP?
• RAD?
• XP ?
• FliP ?
•
•
33 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Management – The Solution
• An clear vision
• An evolving project plan
• An evolving functional specification
• An evolving risk list
• An evolving test plan
34 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
A Clear Vision
• Storyboarding / Wireframes– The Topic– The Classifications– The Specific Ideas
• Non-Functional Models
• Evolving Simplified Documentation
35 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Storyboarding
• Team of 5-7 people
• 45 minutes to 1 Hour at most
• Visually represent your ideas
36 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
An evolving project plan
• Reality Check (Resources, Time, Quality)
• Don’t be afraid to change the plan !!!
• Pick any 2:– Fast.– Good.– Cheap.
37 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
The Plan
• What You Gonna Get?
• By When?
• How You Gonna Get there?
• How Much It Gonna Cost?
38 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
The Initial Plan
• The specification of what the final product or service will be capable of doing;
• The top-level plan for how everything is going to be done and how it will all fit together.
• The timetable of when the client can expect to be able to see and evaluate specific parts of the finished product.
• The budgets associated with those timetables
39 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
The Plan
• Differentiate the major tasks from the little stuff; group minor related tasks under the major tasks.
• Sequence the major tasks into some logical progression.
• Figure out who’s going to do which task(s) and what they’ll need to get it/them done well and right and about how long your team members think they will take to get done. Add 50% (build in the time cushion).
• Advise those people what you want done, but not necessarily exactly how you want it done. People’s creativity will amaze you sometimes.
40 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
The Plan
• Too Much Detail
• Not enough Detail
• Project and Product summary – Plain English– Who’s who
41 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Risk Management
“since unplanned network outages are a big inconvenience, in the future I should be notified in advance of all unplanned outages...”
42 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Plan your Risks
• Believe in Murphy What can go wrong, will
• Think about it• Plan for it• Accept it
• Find your constraints
43 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Plan your Risks
• You don’t get enough money.
• You don’t get enough time.
• You don’t get enough people.
• You get the wrong people
• Your client is inaccessible.
• There are too many cooks.
• “Circumstances beyond your control”.
44 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Roles - Introspective Roles
• Product focus.
• Project focus.
• Task execution focus.
• QA and testing focus
• Structural focus.
• Documentation and training focus.
45 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Roles - Extrospective
• Client/Customer liaison.
• Sponsor liaison.
• Business point-of-contact.
• “Infrastructure”/maintenance liaison.
46 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Estimating time
• There are three major ways projects get scheduled:
• Top-down;
• Bottom-up; and
• Dictated release date.
47 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Keeping Track of it all
• Show and Tell instead of Reports
• MBWA
• Email, Email, Email !!! (or IM/ICQ)
48 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Communication
• Good Reports– Short– Contain Summary– Have pictures !– One page long
• Too much information is– (a) useless, or– (b) distracting, or– (c) all of the above
49 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Using Time
• You CANNOT manage time, you can only use it
50 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Using Time - Meetings
• No specific objective (“We always meet on Tuesdays at 11.”);
• No agenda (“Well, we’re all here, what shall we talk about today?”);
• Too many participants or wrong participants
• Too long
• Failure to control the meeting , lack of focus
• No closure
51 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Using Time - Meetings
• Meetings should be between 30 and 50 minutes
• Always have someone take notes, if you can’t find some one, buy a tape recorder.
• If possible have daily startup meetings
• Only invite those who have something to gain or contribute.
• END and Start on time
52 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Overtime
53 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Testing
• Feature Reliability
• Usage and Functionality
• Integration Testing.
54 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Horror Story #3
• Call Accounting system• Project late, pressure to get things done earlier• Management thinks money can drive productivity• Spaghetti code• Planning inconsistent• CEO wanted to manage the project, no PM
experience• Multiple teams in several physically separated
locations
55 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Horror Story #3
• What is essential• What is the goal• Modularize the existing code, even if it is working• Small tasks – get a feature working perfectly• Reuse of modules once the first feature was
working
• When re-architecting project mid stream do in simple form, not as complete as done at the beginning of the project
56 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Recovery
• Stop. If you Know something is wrong, stop doing it.
• Consolidate all of the information in one central location … computer and non-computer. Make it all available to all of the team members.
• Find out what the goal is. The business goal. The technical goal.If it doesn’t get you closer to a business or technical goal, forget it.
57 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Recovery
• People … remove problematic people. Don’t task them or give them non-critical tasks if can’t get rid of them
• Team morale. Most important. To improve … listen to the team, back them up. Avoid burn-out – make them leave the office.
58 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Recovery
• Reschedule if possible. Phased launch. Build-every-night – small attainable goals. Regression testing – automated testing tools. Release in the morning instead of at night.
• Communications – ask the team what is wrong, respect their opinion.
59 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Project Recovery
• Get a decision maker at the executive level with a scheduled time to make decisions. If not available, project gets delayed.
• Create a project log, why project not getting done. Any documentation better than no documentation.
• Do not commit to a new schedule, especially within 2 weeks of the recovery period. After 2 weeks you can usually get them a new schedule.
60 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Why CF programmers Rock !!!
• We focus on Results
• We produce Results
• We can change code easily
• We usually avoid complexity
• We help each other, we learn quickly
• We just “Rock”
61 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools
• Web Based tools
• SiteSpring (discontinued)
• Knowledge management
• Microsoft Project
• Online project management
62 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools – Simple Project Site
63 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools – Simple Project Site
64 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools –Simple Project Site
65 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools –Simple Project Site
66 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools –SiteSpring
67 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools –OnProject
68 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Tools –Microsoft Project
69 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Sites
• http://www.construx.com/
Steve McConnel
• http://www.shoottheprojectmanager.com/
Robert Brents
• http://www.extremeprogramming.org/
70 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Books
• “The Inmates are running the asylum” • Alan Cooper
• “Rapid Development” • Steve McConnel
• “Necessary, but not sufficient” • E. Goldart
• “The Mythical Man Month” • Frederick P. Brooks, Jr.
• “Extreme Programming Installed”• Ron Jeffries, Ann Anderson, Chet Hendrickson
71 © Shlomy Gantz 2002 Project Management for the MX generation http://www.shlomygantz.com
Q & A
Shlomy Gantz
http://www.shlomygantz.com