1. Cost Problems
1.1. Cost more than expected
1.1.1. Because of things were forgotten
1.1.1.1. SOLVING
1.1.1.1.1. list all the tasks required in a project
1.1.1.1.2. Involve everyone who's gonna be working on the project
1.1.1.1.3. Random brainstorm first, then put it into a systematic diagram
1.2. the failure to generate accurate cost estimates.
1.2.1. SOLVING
1.2.1.1. do something twice
1.2.1.2. don't use the average, don't use the lowest estimate
1.2.1.3. DONT dishonest to add a safety margin on
1.2.1.4. don't add just 10% but add halfway between the average and the worst
1.3. scope creep, the addition of small, extra features to your project
1.3.1. SOLVING
1.3.1.1. to be assertive
1.3.1.1.1. if the customer says, "Can you do this extra thing?" you must say, "Yes we can do it, "but we would have to charge you for that."
1.3.1.2. say, "Everything must be signed for."
1.3.1.2.1. having a Change-Request form
1.4. overspending without realizing that you're overspending
1.4.1. SOLVING
1.4.1.1. control the spend profile
1.4.1.2. control the progress
1.4.1.2.1. Have they done what they should've done in that first year?
1.4.1.2.2. make Gantt chart
2. Lateness Problems (Time Problems)
2.1. get some of your dependencies wrong or you miss a dependency between one task and another
2.1.1. SOLVING
2.1.1.1. create a network diagram
2.1.1.1.1. Post-It Note diagram for obvious reasons
2.1.1.2. create Grantt chart
3. Communication Problems
3.1. Teams
3.1.1. they push you into agreeing to the impossible at the start
3.1.1.1. SOLVING
3.1.1.1.1. make Gantt chart
3.1.1.1.2. kick-off meeting
3.2. Suppliers
3.2.1. they say they'll deliver parts by certain dates and then they change/late
3.2.1.1. SOLVING
3.2.1.1.1. Communication plan
3.3. QUESTIONS FOR SOLVING
3.3.1. How are your communications with your team, your suppliers, and your customers?
3.3.2. Have you got a communications plan agreed with them?
3.3.3. Could you be using your Gantt chart more as a communication tool?
4. People Problems
4.1. Skateholders
4.1.1. different stakeholders, different ideas
4.1.1.1. SOLVING
4.1.1.1.1. 2 kick-off meeting
4.1.1.2. QUESTION FOR SOLVING
4.1.1.2.1. Were you assertive enough at the meeting?
4.1.1.2.2. Did you even have a meeting?
4.1.1.2.3. Did you get it properly written down?
4.2. Our team members
4.2.1. not engage with project
4.2.1.1. SOLVING
4.2.1.1.1. involving your team as much as you can
4.2.1.1.2. make plan together
4.2.1.1.3. dont under-estimate them
4.2.1.2. QUESTIONS FOR SOLVING
4.2.1.2.1. Is your team fully involved as much as possible?
4.2.1.2.2. Are there any individuals who you've left out?
4.2.1.2.3. Are there any stages of the process where you could involve your team more?
5. Quality Problems
5.1. customer being unhappy with what they get delivered at the end
5.1.1. SOLVING
5.1.1.1. clearly define at the start what the customer's gonna get
5.1.2. QUESTIONS FOR SOLVING
5.1.2.1. Have you defined everything in writing at the beginning?
5.1.2.2. And if not, it's never too late to send them a clarification email saying, "Can I just be really clear "about what this part here means?
5.2. How to define quality (Quality is not satisfy)
5.2.1. SOLVING
5.2.1.1. determine how good they are (Scope)
5.2.2. QUESTIONS FOR SOLVING
5.2.2.1. What are we gonna get?
5.2.2.2. And how do we measure the quality of each of those deliverables?
5.2.2.3. So maybe you could think about the project you're working on at the moment and just ask yourself, "Have I clearly defined everything that the customer's gonna get?
5.2.2.4. And for each of those things, what are the attributes that define the quality of those items?"