PMI® Switzerland Chapter


Chapter Communications Blog

PM Conference Team is Calling All Changemakers



We are a team of 25 volunteers committed to making 11th PMI Switzerland's conference a great experience. Do not miss it. We are looking forward to meeting you.

As soon as you arrive, we will welcome you and make you feel as if you know everyone already. Your day will start with breakfast networking, ensuring you are fully awake. Next is the welcome session. Besides the last minute news, you will learn about PMI Switzerland’s 2022 objectives and activities.

Two morning keynote sessions will help us dive into the worlds of AI and Organizational Transformation. During lunch break, you can network with other participants, but also visit the booths and learn more about our sponsors, partners and the latest PMI offerings. In the afternoon, we are offering you mini workshops where you can learn and practise agile and transformational methods and practises.

In the closing session, you will hear about Microsoft and PMI collaboration.

Networking dinner combined with additional informational sessions will be a very nice ending of this exceptional day. And we are preparing marvelous surprises for you. With a bit of luck, you can win quite valuable prizes. It’s too early to tell you everything but rest assured we are doing everything not to disappoint you.


If you are unsure whether you should attend, get in touch. Let us tell you more about our preparations and help you make the right decision.


Best regards,

Adi Muslic

VP Sponsors & Partners and PM Conference organization lead


Editorial PMI Switzerland Newsletter July 2022

Author: Philip Springuel, PMP

Philip Springuel NEW 100x100

Dear friends, colleagues and volunteers,

This month’s PMI Switzerland newsletter gets you started on your summer break. We offer a quick reminder to register and attend this week’s Afterwork Networking, 5 July at White Horse in Lausanne. Equally important, we invite you to save the date for the upcoming 11th PMI Switzerland PM Conference, to be held 21 September.

Featured in this month’s newsletter is Can Izgi’s most welcome article: Four Myths About Agile, which will reassure many of us about succeeding with agile projects.

Also find 5 new member profiles in this newsletter.

Finally, for the upcoming 2023-2024 PMI Swiss chapter election term, we call on active PMI CH members to contact us if you are ready for action, collaboration with great people and a lot of fun! Read the article for application details and contact information. As always, find much more about PMI Switzerland on our website and social media channels.

Wishing you success ahead and a pleasant summertime.

Philip SPRINGUEL, PMI Switzerland Newsletter Copy Editor

Save the date 11th PMI CH Conference 21 September

Authors: Adi Muslic, PMP and Valerie Pierre, PMP

Adi Muslic 100x100pix     Valérie Pierre

PMI Switzerland is delighted to announce the 11th edition of its PM Conference.

The conference will be held in person at PwC Zurich, Sophie-Taeuber-Strasse 14, CH-8050 Zürich on Sep 21, 2022, under the theme “Innovation in Project Management - Shaping the Future of Projects”. 

There are voices out there who claim that “project management is dead”. We don’t believe in those rumors at all! Project management is alive and kicking, but it will certainly evolve and adapt due to new technologies, changing market forces and societal changes.

What impact are the new technological breakthroughs having on the role and skills of project management practitioners? What forces are at play and how can project managers best equip themselves for what’s to come? As the global demand for project managers keeps increasing, it is all the more important for project managers to anchor their position as strategic leaders and change agents in today’s workplace and be at the forefront of innovation to shape the future of the project management profession.

Join us in Zurich for a full day of dedicated time to learn about the latest trends and get an outlook on the future of project management. Get inspiring insights from thought leaders and get hands-on practice during the breakout sessions. Be part of the PM community and exchange ideas and good practices on how to shape the future of the profession!

The conference will host a variety of speakers, workshops, exhibitors, and a networking dinner for all attendees. 


Registration details are coming soon.

Save the date and stay tuned for more information!

Add the date to your calendar: Sep 21, 2022


Register to our event mailing list and stay informed

Four Myths About Agile

Author: Can Izgi, PMP, PMI-ACP, PSM I

Can Izgi

I deliver a lot of Agile courses. There are some questions that come up in my lectures, which are the result of myths people believe about Agile. Some of these myths are related to the misinterpretation of the Agile Manifesto. Below we see the four values of the manifesto: 

Manifesto for Agile Software Development

We are uncovering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

© 2001, the Agile Manifesto authors


In this article, I will give explanations related to the following keywords seen in the manifesto: processes, tools, documentation, contract, and plan. Experienced Agilists are aware of these myths.


MYTH: It is very unlikely that an Agile team is going to follow a process or use a tool during a project.

FACT: Agile teams follow processes and use tools regularly.

For example, Scrum has the following workflow:

… → Sprint Planning → Sprint Execution → Sprint Review → Sprint Retrospective → Sprint Planning → … 

On the other hand, one of the core properties of Kanban is “Make process policies explicit.” Core Kanban properties are: 

  1. Visualize the workflow.
  2. Limit WIP (work in progress).
  3. Manage flow.
  4. Make process policies explicit.
  5. Utilize improvement opportunities.

Agile teams use tools like Jira, Agilean, Agilo, etc.


MYTH: Many Agile teams finish projects without preparing any documents.

FACT: It would be impossible for an Agile team to finish a project without preparing any documents.

Examples of documents include Product Backlog, Sprint Backlog (which includes a task list), Definition of Done, Improvement List (which is updated during the Sprint Retrospective), Test Documents, Process Policies (in Kanban), Project Charter, Product Roadmap, Release Plan, Stakeholder Register, Risk Register, etc.

The Agile approach to documentation consists of “just enough,” “just in time,” and “just because.”


MYTH: It is extremely difficult to come up with a contract model which would be suitable for Agile projects.

FACT: Many contract models are being used successfully in Agile projects. 

Here are two examples:

Example 1 – Fixed-price with an early termination option clause (money for nothing): The customer can terminate the project early if they pay a predetermined portion of the remaining contract value.

Example 2 – Graduated fixed-price: Different daily rates are used based on early, on time, or late delivery.


MYTH: High performing Agile teams generally spend negligible time for planning activities.

FACT: High performing Agile teams always spend a lot of time for planning activities.

Many experts believe that, on average, an Agile team ends up doing more planning compared to a Waterfall team, but the planning activities are distributed differently over the project life cycle. Agile planning is less of an up-front effort. Although the teams prepare product roadmaps and release plans, most of the planning activities focus on smaller horizons. This approach is called rolling wave planning.

Agile teams uncover requirements continuously by trial and demonstration, which will require replanning, and midcourse adjustments are the norm.

In Scrum, the Sprint Planning meeting is timeboxed to a maximum of eight hours for a one-month Sprint. In Kanban, the teams conduct Kanban Replenishment meetings. Daily planning activities are present in both Scrum and Kanban, which are called Daily Scrum or Kanban Daily Standup.



There are many myths people believe about Agile. Some of these myths are related to the misinterpretation of the Agile Manifesto. In this article, I explained the myths related to the following keywords seen in the manifesto: processes, tools, documentation, contract, and plan.

Our Articles By Dates