Skip to main content

Dive deep into Product Management, Product Ownership and Creating Great Products


I have become really excited about the potential of bringing an excited, passionate group of experts into room to work on challenges and problems that inspire them! So I am really excited about the Product Owner Camp in Switzerland!

Product Owner Camp in Switzerland (#POcampCH) is an Open Space conference inspired by the successful Agile Coach Camp in Kandersteg and Scrum Coaching Retreat in London. Unlike its role models, #POcampCH focuses on product creation: "Product Management meets Product Ownership: How do we create great products together?"

Thursday kicks off with an optional master class, "How to Get Quickly from Idea to Minimal Viable Product?" led by Karen Greaves, Samantha Laing, and Steve Holyer. Social activities are planned Thursday and Friday evening for attendees to interact, learn, and get to know each other.

Friday and Saturday, all day, involve all participants to conduct a series of parallel sessions addressing current topics around product creation and development in a Scrum/Agile/XP/Lean/Kanban context. As an Open Space "Unconference" event, the participants define the program. This is an exceptional opportunity for Agile leaders to collaborate and learn from each other. Saturday afternoon is a wrap-up of the POcampCH that involves attendees retrospecting on the event and looking toward the future.

Target audience

The Product Owner Camp in Switzerland is for practitioners involved in product creation, from the idea to the realization. Product Managers, Product Owners, Designers, Developers, ScrumMasters, Agile Coaches, Testers, Entrepreneurs, Innovators and Managers. Not on the list? No worries! If you create new products, POcampCH is for you!

As a Scrum Alliance sponsored event, you can earn Category A SEUs toward your Certified Scrum Professional.

Prices start at CHF 299 / person in double occupancy (yes, this includes your hotel costs!) or CHF 368 for single occupancy.

Dates: June 11 (18:00) to June 13, 2015 (17:00). Optional all-day Master Class on June 11. For more information, registration, and to find out who else is coming, see http://pocampch.org/!



Comments

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …