[MUSIC] Hi, I'm Ken Wong. Welcome to the Agile Planning for Software Products Course. The fourth in the Software Product Management specialization. This course is intended to be taken after you've completed the course in Software Processes and Agile Practices. Plus the course on Client Needs and Software Requirements. Those two courses serve as the legs in the inuksuk that depicts the structure of our specialization. This course, then, will serve as the body of the inuksuk, placed upon the legs to further complete the structure. In this segment, I'll give you a preview of the Agile Planning for Software Products course. I previously said that making better software involves three goals, the right product, done right, and managed right. This course focuses on Agile planning techniques, so that the project for the software product is managed properly. Is about organizing work effectively while being adaptive to change. Through the techniques we will share with you in this course, the software processes and agile practices are done right, to ultimately achieve the right product. This course brings together many fundamentals from the prior two courses. For example, you'll recognize the concepts of user stories from software requirements, sprints from the scrum methodology, and task dependencies from processes. This course builds upon those concepts. Whether you manage a team of people directly or through others, you will appreciate three key types of planning involved in software projects: Release planning, Iteration planning and Risk planning. We will cover these in Modules 2, 3 and 4, of this course. In the first Module, Morgan Patzelt will outline uncertainties that projects need to resolve. She will also show how to break down work in to manageable pieces. She will also explain the difference between an estimate, a target, and a commitment. In the second module, Bradley Poulette will explain how to use story points to estimate the size of a requirement. He will also explain how estimates relate to velocity as a way to measure the productivity of a development team. It will show how to use time boxing as a basis for planning work, which can then be made into a Gantt chart. This leads, then, to constructing a Release plan to map out the delivery of user stories over the upcoming sprints. In the third module, Morgan returns to describe how to estimate task times and determine task dependencies. She will show how to use CPM diagrams and PERT charts to plan work at the task level. This leads to constructing an Iteration plan to map out the tasks to be done within the next sprint. In the fourth module, Bradley will detail problems or risks that could cause a project to fail. He will describe a number of anti-patterns which are situations with negative consequences for a project and its people. He will outline how to assess risks and determine what level of action is needed. This stage to constructing a risk plan to map out what to do should a risk occur. By the end of the course, you will have gained an effective set of techniques to help you plan your next project and to create a great software product, one that is managed right.