This is my current description of the Scrum Professional course. It is my main offering for the CSP certification.

I want to improve it. Could you comment please? Basics: 1. 2 day course (with exercises, etc.). 1 day workshop (described below). 2. All participants have a CSM or CSPO. And some experience. 3. Course has 16 segments. 4. We want some adaptability, so that the course can be tailored to the participants. Desired Outcomes: 1. Participants will do Scrum more successfully in the real world. 2. All are being advocates of Scrum. Maybe each person in a different way. 3. They see Scrum as needing to add other things (XP, Lean, etc.). 4. We have opened up topics for further learning. We do not expect Participants to be or become masters of the subject. We expect them to be intermediate, and trying to become better intermediate players. This also means they are far more knowledgeable them someone who has read one book or one article, or played for one month on a Scrum-Butt team. Things to choose from for the 16 segments: 1. The basics of Scrum and how to present them. 2 segments. 2. The underlying principles. Why Scrum works, and all the reasons why each practice is useful. 3. The roundedness of a good ScrumMaster 4. Favorite Scrum Mistakes 5. Removing impediments more aggressively; making better business cases. 2 segments. 6. The importance of the Product Owner. Improving the product owner. Making the PO a full member of the Team. 7. Business Value Engineering 8. Joes approach to agile release planning and release plan refactoring 9. The agile contract (fixed-price issues) 10. Patterns of implementer (doer) evolution 11. Using XP in Scrum 12. Fearless Change. 2 segments. Manns/Rising. Kotter. Advocating for the agile team. Advocating for the Agile Transformation. Managing resistance, especially from the middle managers. 13. How to manage the chickens 14. The IRT (Impediment Removal Team) 15. What to do with managers 16. Patterns for the agile transformation 17. What does the broader Agile Transformation look like? 18. Scaling 19. Distributed Agile

20. Lean Ideas in Scrum 21. Too many projects at once; Focus on one project at a time 22. Kanban and Scrum (aka Scrumban) 23. Taking the Scrum meetings to the next level 24. Taking the artifacts to the next level 25. Managers and Metrics 26. Knowledge workers and motivation 27. Hyper-productivity 28. Everything is not agile yet; what do we do? 29. What is the secret sauce? 30. Other problems or impediments, as identified by the attendees 31. Team presentations. A person or a team presents on their own topic. Below I try to explain each segment. Some basic ideas: People learn best what they want to learn. It is essential to have them actively engaged. Often by doing something. Thinking, talking, discussing, creating. AND People want and need to also hear from the leader. People will be at different levels of experience. Often one person will be great in one area, but weak in another area. EXPLANATIONS OF THE SEGMENTS. 1. The basics of Scrum and how to present them. 2 segments. We find that success is mainly based on the basics. In American football, we call this the basic blocking and tackling. We also find that there are always substantial misunderstandings of the basics in any group. And we find that people need more experience explaining the basics. So, we do an exercise where they explain, quickly, the basics to each other. And find they disagree on the basics. And then we hopefully fix those mis-understandings. 2. The underlying principles. Why Scrum works, and all the reasons why each practice is useful. We discuss the agile principles. Remarkable how we have forgotten them. And remarkable how important it is to do the practices with the right principles in mind. Again, explaining these principles is also often hard to do. And it is remarkable how many good agile people actually disagree on a few basic principles. 3. The roundedness of a good ScrumMaster

Here we discuss all the attributes of a great ScrumMaster. And that it is impossible to be a perfect ScrumMaster. So, we try to prioritize. What are the most important things to improve on now? NOTE: Descriptions of topics below to be added 4. Favorite Scrum Mistakes 5. Removing impediments more aggressively; making better business cases. 2 segments. 6. The importance of the Product Owner. Improving the product owner. Making the PO a full member of the Team. 7. Business Value Engineering 8. Joes approach to agile release planning and release plan refactoring 9. The agile contract (fixed-price issues) 10. Patterns of implementer (doer) evolution 11. Using XP in Scrum 12. Fearless Change. 2 segments. Manns/Rising. Kotter. Advocating for the agile team. Advocating for the Agile Transformation. Managing resistance, especially from the middle managers. 13. How to manage the chickens 14. The IRT (Impediment Removal Team) 15. What to do with managers 16. Patterns for the agile transformation 17. What does the broader Agile Transformation look like? 18. Scaling 19. Distributed Agile 20. Lean Ideas in Scrum 21. Too many projects at once; Focus on one project at a time 22. Kanban and Scrum (aka Scrumban) 23. Taking the Scrum meetings to the next level 24. Taking the artifacts to the next level 25. Managers and Metrics 26. Knowledge workers and motivation 27. Hyper-productivity 28. Everything is not agile yet; what do we do? 29. What is the secret sauce? 30. Other problems or impediments, as identified by the attendees 31. Team presentations. A person or a team presents on their own topic. !