Summary of scott berkun's making things happen

Please note: This is a companion version & not the original book. Sample Book Insights: #1 We tend to be late. We believe that being on time isn't about targeting a specific moment but instead is about being within a range of moments. Many projects come in late because we tend to estimate based on weak assumptions, predict outcomes based on the best possible circumstances, and simultaneously avoid placing confidence in schedules we see or create. #2 The first purpose of a schedule is to make commitments about when things will be done. The schedule serves as a contract between every person involved, confirming what each person is going to deliver over a particular period of time. #3 The third purpose of schedules is to provide a tool to track progress and break work into manageable chunks. With this in mind, it's time to explore software methodologies. #4 There are many different systems for how to plan and manage the development of software. They are often called methodologies, which means a body of practices aimed at achieving a certain kind of result.