Articles

This is the third in a series of posts exploring Scrum Mastery. In our first post, we introduced the 4 dimensions of Scrum Mastery. In the second post, we explored how to grow a strong team identity. Now we will explore the team process dimension.

How Do You Work as a Team to Maximize the Benefits of Scrum and Agility?

Recall that the Scrum Team defines their own process within the boundaries of the Scrum framework. This includes their practices, tools, interactions. This includes how they fulfill the accountabilities of their Scrum roles and how they utilize the artifacts and events.

Source de l’article sur DZone (Agile)

« An Agile Coach know more than just Scrum, » said one consultant in a boardroom meeting, « he/she knows organization dynamics, executive coaching and other Agile practices like Kanban and DevOps, » he continued.

« Stay silent, no need to correct him in this kind of forum, » my inner voice said. « Take a deep breath. »

Source de l’article sur DZone (Agile)

"To simplify yields a richer result." — Yvon Chouinard, Let My People Go Surfing

This is one of my favorite quotes of all time. Throughout life, I am constantly learning through trial and error. And I have found that the simple process often leads to the better product. For instance, my barbecue chicken recipe. I love summer and enjoy spending time with friends and family barbecuing. I have a simple recipe that is my go-to, but I’ll often try to shake things up with new sauces, rub mixtures, or brines. Turns out that my simple recipe with a minimal amount of ingredients is always the crowd favorite.

Source de l’article sur DZone

A common question I hear in Scrum training courses and in coaching sessions is, "How much Product Backlog refinement should we do and how much detail should be in the Product Backlog?"

First, let’s look at the Scrum Guide.

Source de l’article sur DZone

As a Product Owner, you are responsible for Product Backlog management, stakeholder management, and forecasting. Therefore, you will probably use a variety of tools and techniques to track progress, manage expectations, and keep people informed. One of the tools that may come in handy for you is a product roadmap. Applying product roadmaps effectively can be challenging, however. The concept of a product roadmap is that it is a high-level, strategic plan, that describes the likely development of the product over a given period of time. The roadmap should support the products’ purpose and vision and it helps the Product Owners to keep their stakeholders aligned. The roadmap also makes it easier to coordinate the development of different products and it fosters transparency in order to manage customer expectations.

In a lot of organizations, I see that Product Owners are focused mostly on developing features and therefore, a lot of roadmaps are also dominated by features and functionalities to be delivered. The disadvantage of focusing on features too much is that there are always too many features that would add value, therefore creating a lack of focus on the vision and goals. By focusing on the features too much, the roadmap will turn into an overloaded product backlog, instead of a high-level, strategic plan for the products’ future development.

Source de l’article sur DZone

Here I am sitting in my hotel room while looking at my half-empty wine glass and the stars outside while preparing for my last Professional Scrum Master (PSM) class for the year 2017 and pondering about all of the classes I have facilitated over this year. PSM has been a transformational course for me because it has changed me by seeing how it has changed the life of many of my students. 

Starting from the end of 2017, Scrum.org has put more emphasize on servant-leadership for Scrum Masters. After all, the Scrum Guide explained that the Scrum Master is the servant leader of the Scrum team and the organization to which she belongs.

Source de l’article sur DZone

Testers + Scrum = ?

Several times I’ve had conversations with people who work with Scrum or Agile methodologies who claim they don’t have testers and don’t run into any problems. On the other hand, I have seen testers within these schemes who often feel excluded from the development team. Other testers who have not yet worked in Agile teams question whether there is even room for testers in Scrum.

It’s often touted that everyone in a Scrum team is able to perform different tasks and that all are responsible for quality. But, there are some things that a tester can handle better than others. For example, writing good acceptance criteria requires a tester skillset, as one must keep in mind and worry about certain characteristics such as quality, testability, maintainability, etc. These are all things that the tester role is responsible for obsessing over. Therefore, when you need to write acceptance criteria, you’ll be better off delegating it to someone trained in testing over someone that’s not.

Source : https://dzone.com/articles/can-there-be-testers-in-scrum?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fagile

Selon la méthode agile SCRUM, les développements applicatifs sont organisés selon une récurrence de « Sprints », cycles de développements partiels.
Pendant un Sprint, des réunions appelées « Scrum » établissent le point d’avancement des travaux depuis la dernière réunion et organise la suite jusqu’à la réunion suivante.
Chaque Sprint se termine par une phase de test des fonctionnalités livrées « en l’état ».
Le « Backlog » de produit référence les fonctionnalités implémentées.

Le fait de livrer « au fil de l’eau » les modules applicatifs réalisés permet de vérifier l’appréciation du « client » à chaud et d’opérer sans attendre les corrections et ajustements, dans une situation de correctifs mineurs.