Barry Flicker: Slashing project time by 10% or more (70 Mins)
http://itc.conversationsnetwork.org/shows/detail1721.html
Anyone ever worked on a team that didn't work, this talk will some shine light on what could have happened (especially in IT).
Here are the points of the talk, the following doesn't even cover half of it:
--------------------------------------------------------
The need to plan:
When Living in the bleeding edge in time for projects; It's like 'Building the plane, while it’s in the air'. What happens if the landing gear was missing -> it ends up in project failure
The need to be clear:
A way to minimize/clear up misunderstands & bad assumptions. It's to setup a common language & make sure in every meeting everyone understands:
1. Goals
2. Role/Responsibility
3. Process
4. Outcome
Have a key project statement to communicate with stakeholders or anyone new to the project; it keeps the aim clear.
-------------------------------------------------------
Project failures: Unrealistic deadline
If we consider the opposite, there is something in how we are behaving that is affecting the situation.
But now we can help the situation & it's no big deal to change our behavior to improve the condition.
------------------------------------------------------
What is Project management?
(Project management is not using MS Project, not even close)
1. Tool-set: It magnifies what you do
2. Skill-set: To communicate, lead, listen & negotiate effectively
3. Mind-set: Change people mind in thinking planning is not “a waste of time”
If no skill-set or mind-set, we are Idiot with powerful tools -> It only make us dangerous, not better.
--------------------------------------------------------
Advises from Q & A:
Some Statistics:
Anyone ever worked on a team that didn't work, this talk will some shine light on what could have happened (especially in IT).
Here are the points of the talk, the following doesn't even cover half of it:
--------------------------------------------------------
The need to plan:
When Living in the bleeding edge in time for projects; It's like 'Building the plane, while it’s in the air'. What happens if the landing gear was missing -> it ends up in project failure
The need to be clear:
A way to minimize/clear up misunderstands & bad assumptions. It's to setup a common language & make sure in every meeting everyone understands:
1. Goals
2. Role/Responsibility
3. Process
4. Outcome
Have a key project statement to communicate with stakeholders or anyone new to the project; it keeps the aim clear.
-------------------------------------------------------
Project failures: Unrealistic deadline
- Bad Expectation: Upper Management
- Inadequate Resources: different demands & needs used by other departments
- Scoop Creep: Sliding in addition items
- All explanation = It’s not us, it’s them (The idiots out there)
If we consider the opposite, there is something in how we are behaving that is affecting the situation.
But now we can help the situation & it's no big deal to change our behavior to improve the condition.
------------------------------------------------------
What is Project management?
(Project management is not using MS Project, not even close)
- Core: The process to make & keep clear commitments
- Foundation: Building on relation of Mutual trust & respect
- Tools: Use to identify & track commitments
1. Tool-set: It magnifies what you do
2. Skill-set: To communicate, lead, listen & negotiate effectively
3. Mind-set: Change people mind in thinking planning is not “a waste of time”
If no skill-set or mind-set, we are Idiot with powerful tools -> It only make us dangerous, not better.
--------------------------------------------------------
Advises from Q & A:
- Time Estimations: They are best guess only, should not set in stone; especially not early in the game.
- Missing the Small Stuff: Use a ground-rules check list to make sure the little things are missed. Example: Hardware-software delay of 2 weeks, due to board not shipped from hardware team to software team
- Brain-dead Behaviors: When you see someone acting in a brain-dead way, this means that you are seeing the whole picture, while others are not; Ask yourself what's the pay-off? What's the missing information?
- Resistance to Accountability: People keep getting punish for taking accountability, that's fear based. Instead bring to together the team & talk about how to solve the problems; then accountability will arrive to take on the action.
Some Statistics:
- 51% of ERP implementation are unsuccessful
- 75%+ IT project were delayed 30% more
- 52% cost run over 189% of the estimated cost