Summary
In this chapter, we introduced a case study, the Mercury program, which will build a P2P messaging application across multiple ecosystems. We then used that case study to explore a simple program charter and the intersection between the Mercury program and its projects. We looked at how the audience level can change what a status report will contain and the tone that it carries. Lastly, we dug deeper into key management areas and refined the definition and roadmap of the Mercury program as a result.
In Chapter 5, Driving Toward Clarity, we’ll explore one of the most important characteristics of a successful TPM. This ability of a TPM to take an ambiguous situation and find or define clarity is what helps us solve problems, find opportunities to reduce risks, and deliver results.
Additional resources
You can find templates regarding project and program charters in the GitHub repo related to this book. Please check the Preface for the GitHub link.
