Scrum
Get flash to fully experience Pearltrees
En route vers l'agilité, SCRUM et XP retour d'expérience
Voici un parcours initiatique vers les méthodes agiles, l'apprentissage d'une quête de l'excellence et de l'amélioration continue, une série d'épreuves pour devenir meilleur … 7 commentaires · The power of Scrum By Radwane HASSEN Cet article n'est ni plus ni moins que ma feuille de route, voici comment j'ai commencé à m'intéresser à l'agilité et surtout comment j'ai procédé pour l'intégrer dans mes développements et dans mon équipe.
Goal: Think of Effective Improvements for Your Iteration Iteration retrospective activities are tricky; it is often difficult to think of practical improvements, and reflecting on negative aspects of the project can leave your team feeling upset and unmotivated. A great way to prevent these from occurring is to play a game that focuses on the positives while also pointing out aspects that need to be changed. As described in Diana Larsen and Esther Derby’s Agile Retrospectives , Learning Matrix does just this. In this game, teams collaborate to identify what they liked and disliked about a past project, and to point out whom they appreciated and what they believe should be altered for the future. Whether analyzing the results of a conference, product, or meeting, Learning Matrix can help you uncover your top-priority items to enhance your iteration.
Learning Matrix - Innovation Games
Scrum is a great agile management framework for iteratively developing complex software systems, and it works well in many circumstances. Certain problems can arise, however, such as a highly fluid product backlog, which make kanban’s emphasis on backlog flexibility a more attractive alternative. Software experts like David Anderson, Corey Ladas, Dean Leffingwell, and Linda Cook point to small, loosely coupled user stories with an experienced agile team as key factors for productivity gains using kanban. Yet, few studies exist to show concrete metrics in productivity gain.
A Productivity Comparison of Kanban and Scrum
Is it Time to Stop Estimating User Stories?
Imagine an organization where teams are expected to have a fully estimated backlog in order to determine the cost for the project. At first glance such an approach seems to be a good idea. The people who will do the work will provide the estimate and thus based on what they say the true cost of the work will be known.