Resources

Technologie, Globalisierung, Umwelt und unsere Gesellschaft sind längst eng miteinander verknüpft: Technologische Fortschritte treiben die Globalisierung voran, verändern unsere Umwelt und beeinflussen unsere Gesellschaft.

McKinsey and Scrum.org presented a webinar on joint research about measuring business value. There were a number of questions unanswered. This blog answers those questions.

En este video hemos explicado las métricas Kanban para equipos Agile o DevOps.

In business, the quest for predictability is universal. We all want to grab hold of the reality we face everyday and, somehow, bend it to our will.

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world, a seasoned Scrum Master is nowadays in high demand.

So you have a couple of Scrum Teams that are working in adjacent areas and you're starting to face some challenges in delivering value in a coordinated integrative way.

In this series of ‘In-depth’-posts, we take time to consider the bigger picture. This series is not about easy answers or practical tips, but to develop a more complete understanding of what may be going on.

Scrum se ha convertido en el marco ágil de trabajo más usado en el desarrollo de software en el mundo.

With the launch of the Kanban Guide for Scrum teams in 2018, its 4 flow metrics have gained more popularity amongst the Scrum community.

What I usually hear is “Scrum is great, but it doesn’t work in my organization, because...” and then follows a list of excuses why change is impossible or hard.

A typical Kanban board shows a series of steps or activities that work passes through. Does this mean that Kanban is only suitable for "linear" processes? Scrum is a proven strategy for addressing complex adaptive problems, so if Kanban is linear, is it an unsuitable complimentary practice to add to Scrum?

Late in the second day of my PSM classes, I usually do an exercise with my students about skills and traits.

Agility is not a state. Agility is an ability to change and respond to an environment you're in as an organization.  Once you realize that a binary Scrum-not Scrum stops making much sense.

In our professional world of software development, it is very common someone asking “What is this Agile?”

This podcast tackles some of the question: Scrum vs. Kanban? How about Scrum and Kanban. Why would you want to use both? Scrum is based on Empiricism, Kanban is based on Flow, Flow enhances Empiricism and Empiricism enhances Flow. Take the best Scrum teams and the best Kanban teams and take an average person looking in on them they wouldn't be able to tell the difference.

Executives: there are many reasons for agility. You already know this.

During this virtual event, Louis-Philippe explained the Kanban metrics for Agile or DevOps teams. Although the Kanban delivery strategy is highly recommended in DevOps mode, unfortunately, its metrics are hardly used in our profession. Louis-Philippe therefore wishes to share its value with participants. Back at their workplace, Louis-Philippe hopes that participants will have new tools to answer the client's famous question "When will it be done?" (61 Minutes)

Inspiration for fulfilling the stances of a Scrum Master, remotely.

The COVID19 pandemic gives us plenty of opportunities to think about uncertainty, complexity, and how to deal with those using Empiricism.

This sixth article now dives into organizing a remote Sprint Planning with a distributed team: practices, virtual Liberating Structures, and lessons learned.

Many teams are finding that they need to adjust to a new reality amid the covid-19 pandemic. Strategic plans lie in tatters, urgent unplanned work fills the board, stakeholders are hammering teams with requests, and routine has gone out of the window. This is a time for a Scrum Master to be pragmatic, calm, and outcome focused: providing delivery leadership without allowing process to get in the way.

Completing an Agile Coaching certification doesn’t make you an Agile Coach. So where do you start and how do you chart your own journey?

The premise of Lean Coffee is relatively straight forwarded. Like-minded people that want to create or discuss something they care about use this tool to organize their conversations.

Agile has always been about colocation, about direct communication, physical boards, and all the other haptic and analog moments to create value in the digital realm...

The Old Farmer’s Almanac is the oldest continuously published periodical in North America. It was first published in 1792 by Robert B. Thomas who wanted an almanac “to be useful with a pleasant degree of humor. Many long-time Almanac followers claim that its forecasts are 80% to 85% accurate. 

in today's vlog I am sharing with you how to use Scrum with Kanban.

The emergence of the Kanban Guide for Scrum teams has given new metrics and practices to Development Teams on how they can augment their Sprint Backlog to manage their work.

This article goes into detail how anti-patterns can evolve and possibly create other issues for the Scrum Team.

The 4th survey “Status Quo (Scaled) Agile” now gave some interesting answers helping organizations to position their own agile activities and helping to define an appropriate strategy where and how to use the agile on team level or scaled agile on the level of programs or organizations.

This is a post explaining how to do throughput-driven sprint planning using throughput and Service Level Expectation (SLE).

Why output-oriented metrics are mostly a waste of time in software- and product development.

In this post I want to explore whether the Increment, a core concept to Scrum, needs to be changed for Scrum in a non-IT context. In future posts, I will do the same for the Definition of Done, or other concepts that may provide a better understanding of Scrum when applied to non-IT context.

One of the things leaders often say they want most is predictability. Predictability is defined as the consistent repetition of a state, course of action, behavior, or the like, making it possible to know in advance what to expect.

If you are working as a Product Owner, there is—very likely—room for improvement. This list of some of the most common Product Owner anti-patterns might be a starting point.

In my previous 2 episodes of this series on Systems Thinking, I elaborated on what Systems Thinking is and on the Wicked Problems Systems Thinking is trying to solve. In this episode, I want to explore Complex Adaptive Systems (CAS).

Sprint Planning is a core event, defining how your customers’ lives will improve with the next Product Increment. Learn more on how to improve its effectiveness by avoiding 20 common Sprint Planning anti-patterns.

Students and clients ask us “Can Kanban and Scrum work together?” “Of course!” However, what do you mean by “Kanban”?

Often we work harder in Scrum teams, but not necessarily smarter. Therefore the way we work has to change. Five tips for more effective agile work.

The most important question to stakeholders is often “When can it be done?” There is a lot that goes into answering that seemingly simple question. What is involved in the work?

In this episode of Ask a Professional Scrum Trainer, PST Naveen Kumar Singh answered questions from a live audience.

Within the Scrum process, there are eleven basic elements that make up the framework. 3 roles, 3 artifacts, and 5 events. Practitioners need to learn to apply and understand the principles behind these in order to obtain the full benefits of the Scrum process.

In a series of blog posts, I want to share how you can use Systems Thinking to resolve complex problems such as software teams not delivering the right software fast enough.

In this Scrum Tapas video, Professional Scrum Trainers Louis-Philippe Carignan and Daniel Vacanti who is also the co-creator of the Professional Scrum with Kanban (PSK) class, Kanban Guide for Scrum Teams and Kanban Method discuss the origins of the PSK class and provide some insights into what will be learned over the 2 day class. (3:15 Minutes)

If there is one trend that has surpassed Agile in our profession over the last five years, I would say DevOps would be a good culprit. As we’ve seen an explosion of tools to implement CI/CD in our Scrum teams, we’ve also seen some of our Agile practices being challenged by this new reality.

In this episode of Ask a Professional Scrum Trainer, PST Pawel Mysliwiec answered questions about story points, estimating, the Scrum Roles, the Scrum events, scaling, using Scrum with Kanban and more!

I’ve been teaching the class Professional Scrum with Kanban (PSK) for the last year now and I strongly believe parts of its content will send some of our current practices and books to the Agile museum.

Scrum Master anti-patterns: The reasons why Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. They run from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself.