Do you have an idea you’d like to turn into reality but you’re feeling stuck? Have you ever thought about accomplishing something big, but it seemed too complex? Would you like to be doing bigger and better things in your life, but you don’t know where to start?
Project Management Is The Answer
Cesar Abeid has been there, and it wasn’t until he learned the principles of project management that he was able to start turning his ideas into reality, delivering on his promises, and getting things done. In Project Management for You, Cesar unlocks these tested and proven principles that allow big corporations like Apple and Google to make detailed promises of new products and services to their customer base months in advance, and still deliver it 100 percent of the time.
Easy To Understand
Skipping the corporate lingo and using powerful and colorful stories, Cesar will take you step-by-step through the stages of bringing an idea to reality. Project Management for You will empower you to dream big and have the confidence to turn those dreams into something tangible you can enjoy, be proud of, or even sell!
Life is a Project. You are the Manager. Whether you want to learn the efficacious principles used by companies and individuals around the world to bring new products and services to the market, or whether you want to learn the nuts and bolts of project management, Project Management for You will help you accomplish just that. And in the process, you will realize that life is a project, and you are the manager.
One of the few books where the lessons learned will be applied almost daily. Here is a quick summary of what I learned.
"Project Management For You" book summary by the chapters
1. Composing (Establish Requirements & Deliverables) - When should it be finished? - Why do the project in the first place? (Requirements and basic constraints) - How much $ and time? - Mind map - Create hierarchies 2. Decomposing - Break down into smaller deliverables - Break those down - Lowest level is a "Work Project" you can task, a milestone - One person can do them, 8 to 40 hours to complete, not smaller - Work Projects are nouns, not actions - Deliver the WBS (Work Breakdown structure) - see image in book - Use Back-Planning, starting with the end in mind then working backwards on sequence - Create WBS Dictionary (reference material) 3. Decision Making - Can you delegate stuff? 4. Defining Activities - Break each Work Project into tasks (called "activities" in PM) - Not too important if outsourcing 5. Managing Risk - List your risks - Only Create plans for "High Risk events" (high impact & high probability) - Assign each risk an owner (who is responsible?) 6. Delegating - Decide how to decide and the follow-up process (follow when work projects should be at the 50% completed mark) 7. Estimating Duration & Cost - Prioritize activities (tasks) so they will happen in sequence - Decide on a due date and work backwards - List required: - People/skills - Tools - Materials - Get a range of hours required (ie. 8-12 hours) and a range of budget required (ie. $800-$1200) rather than a hard number for each 8. Communications - Listen - Use visualizations to communicate whenever possible 9. Leadership 10. Doing the Work - Centralize communications (like Azendoo) - Define the process (the touchpoints, deliverables, communications, documentation, software, tracking hours, change management, change approvals) 11. Reviewing - At the 50% mark on assigned work projects, check in with team members 12. Managing Change - What is being requested? - Why? - How will it affect the schedule? - How will it affect costs? - Re-baseline 13. Lessons learned - post mortem - Create a living document so simple rules can be created & lessons learned for the future - Schedule quarterly reviews to look at it 14. Check that Off - Add as a task to declare the project a success or a failure - Finalize payments, reassignments, etc. - Centralize all documents
The author admits that this system is an oversimplified version of Project Management best practices. But that is what most entrepreneurs and freelancers need. I have struggled with project planning ever since I first became a full-time freelancer seven years ago—as many of my long-suffering clients can attest.
Because the method described here is simple, it will be easier for a solo businessperson like myself to implement. I know I'll be referring back to this book often as I work on improving my planning and estimating in the second half of the year.
One of the few books where the lessons learned will be applied almost daily. Here is a quick summary of what I learned.
"Project Management For You" book summary by the chapters
1. Composing (Establish Requirements & Deliverables) - When should it be finished? - Why do the project in the first place? (Requirements and basic constraints) - How much $ and time? - Mind map - Create hierarchies 2. Decomposing - Break down into smaller deliverables - Break those down - Lowest level is a "Work Project" you can task, a milestone - One person can do them, 8 to 40 hours to complete, not smaller - Work Projects are nouns, not actions - Deliver the WBS (Work Breakdown structure) - see image in book - Use Back-Planning, starting with the end in mind then working backwards on sequence - Create WBS Dictionary (reference material) 3. Decision Making - Can you delegate stuff? 4. Defining Activities - Break each Work Project into tasks (called "activities" in PM) - Not too important if outsourcing 5. Managing Risk - List your risks - Only Create plans for "High Risk events" (high impact & high probability) - Assign each risk an owner (who is responsible?) 6. Delegating - Decide how to decide and the follow-up process (follow when work projects should be at the 50% completed mark) 7. Estimating Duration & Cost - Prioritize activities (tasks) so they will happen in sequence - Decide on a due date and work backwards - List required: - People/skills - Tools - Materials - Get a range of hours required (ie. 8-12 hours) and a range of budget required (ie. $800-$1200) rather than a hard number for each 8. Communications - Listen - Use visualizations to communicate whenever possible 9. Leadership 10. Doing the Work - Centralize communications (like Azendoo) - Define the process (the touchpoints, deliverables, communications, documentation, software, tracking hours, change management, change approvals) 11. Reviewing - At the 50% mark on assigned work projects, check in with team members 12. Managing Change - What is being requested? - Why? - How will it affect the schedule? - How will it affect costs? - Re-baseline 13. Lessons learned - post mortem - Create a living document so simple rules can be created & lessons learned for the future - Schedule quarterly reviews to look at it 14. Check that Off - Add as a task to declare the project a success or a failure - Finalize payments, reassignments, etc. - Centralize all documents