AGILE MASTERCLASS MIT JAMES COPLIEN: Certified Scrum Product Owner®
ANECON ist stolz mit James „Cope“ Coplien einen der bekanntesten und einflussreichsten agilen Pioniere und Vordenker für eine einzigartige und exklusive Product Owner Masterclass nach Wien zu bringen. Copliens Arbeiten rund um Organizational Patterns waren die Grundlage für Extreme Programming und Scrum und er gilt weitläufig als Erfinder des Daily Scrums. Lernen Sie was es heißt als Product Owner zu arbeiten, nutzen Sie jedoch auch den Raum um die Hintergründe zu erfahren. Was waren die ursprünglichen Beweggründe Scrum so zu gestalten, wie wir es heute kennen? Wie können wir die ursprüngliche Intention dazu verwenden Scrum effektiver umzusetzen? Die Teilnehmer erhalten eine Scrum Alliance Product Owner Certification. Die Plätze sind limitiert. Melden Sie sich noch heute an!
„Don’t get your Scrum knowledge from behind the barn or pick it up in the alleys. Come prepared to have your stereotypes broken, and come with your questions, and be prepared to have some fun.“
About the Masterclass
A Product Owner embodies the vision for their product, has the final say over product content, and is accountable for the value generated by the product. From this perspective the Product Owner is the CEO of an autonomous corporation comprising one or more Scrum Teams.
This course will immerse you in the vision that Scrum holds for the Product Owner role, taking its foundations from Scrum principles. The Product Owner role is not just a re-tread Product Manager: he or she specifies tests, and builds working prototypes, may specify wireframes and navigation trees. The Product Owner must ensure that the team understands each imminent product increment to the point of having an Enabling Specification— otherwise, the team gets to make it visible that the specs are inadequate and „go to the beach.“ The Product Owner is held accountable for value from the product. Great Product Owners can realize immense satisfaction from guiding a product to add value to some constituency, and to watch their teams respond to their inspirational leadership.
We will cover both the Product Owner’s interactions with stakeholders such as the market and end users, and also with the Development Team. There is a special emphasis on value stream thinking and on tools such as decision structure matrices for managing the flow of value to the market. We will also emphasize the Scrum way of running business, with its essential paradoxes such as the tradeoff between agility and certainty. The course looks at value more broadly than just ROI, taking corporate reputation, team autonomy, and workplace quality into account.
The course is divided into 8 modules: Scrum Introduction; Your Job as a Product Owner; The Product Vision; Building the Scrum Organization; How the Product Backlog Works; Running the Business with a Product Backlog; Kaizen Mind; and a bit on scaling.
Though each CSPO course varies depending on the instructor, all Certified Scrum Product Owner® courses focus on Scrum from a product owner’s perspective. Graduates will receive the CSPO designation. All CSPO courses are taught by Trainers approved by the Scrum Alliance.
Who Should Attend
This is a Scrum Course, and not just a Product Owner course, so it should be of interest to anyone wanting to learn Scrum more from the business perspective than from the engineering perspective. The course richly uses the Scrum Patterns to underscore Scrum’s roots in the Toyota Development Production System, and is independent of the nature of the product (i.e., Scrum is not just for software products). Though we will cover all the basic Scrum tenets, this is in some sense an advanced course in that it explores the deeper foundations behind Scrum’s structures so the attendee will understand why we do things in Scrum, and not just that Scrum-says-to-do-X.
Trainer: James Coplien
James “Cope” Coplien was first known for his pioneering work in C++ and object-orientation while at AT&T Bell Laboratories. Since then he has made broad and widespread contributions to the industry in the areas of organizational development, development process, software testing and debugging, VLSI development, knowledge management, and design. With Trygve Reenskaug, he pioneered the DCI programming paradigm that returns programming to noble roots of honoring the mental models of software programmers and users. His early work on development process was one of the foundations of Scrum.
He is the author of several landmark books and is currently working with a team on “A Scrum Book” which is a rationalized, authoritative description of Scrum. He lives in Denmark with his wife Gertrud, and together they serve the world in Scrum and software architecture consulting. When he grows up, he wants to be an anthropologist.
- The Roles, the Artefacts, and the Events
- Risk Management
Your Job as a Product Owner
- Optimizing Value
- What and When — but not How
- Backlog Refinement
- Definition of Ready
- Sprint Planning
- Definition of Done
- Emergency Procedure
- Sprint Review
- Sprint Retrospective
- The PO as Firewall
- Stakeholder Relationships
The Product Vision
- The „big vision“ and the „operational vision“
- The roadmap
- Securing funcing
Building the Scrum Organization
- The PO Team
- The Development Team
- Hire a ScrumMaster
- The basic flow of work and process improvement
- The Meta Scrum
How the Product Backlog Works
- The Life Cycle of an idea
- The Product Backlog
- Relationship with the Dev Team
- Burn-down Charts
- Responsive Deployment
- The Daily Scrum
- Sprint Goals, and Sprint Goals as the initial Product Backlog Items
- Good Product Backlog Items — by example
- Enabling Specifications
- The Structure of the Product Backlog
Running the Business with a Product Backlog
- Working with Stakeholders
- The Last Responsible Moment and decision structure matrices
- The Product Backlog breakdown
- The Sprint Backlog
- Defect / emergent requirement escalation: normal and advanced versions
- Emergency Procedure
- Fixed-Date PBIs
- Release Planning
- Agile Contracts
- Kaizen Pulse
- Process Improvement
- Increasing value versus increasing productivity