The Minimum Viable Product (MVP) is defined in Wikipedia as “a product which has just enough features to gather validated learning about the product and its continued development.” In this article, Sergiy Andriyenko proposes fives rules to apply successfully a Minimum Viable Product strategy.
DUCAT is a free assessment and benchmarking online tool that aims at creating awareness for user-centered agility and enable companies to easily assess the status of their projects. The tool provides a 360 degrees assessment to investigate the team’s perspective and process. These results are completed with the users’ evaluation of of the product.
As Agile practitioners, we’ve learned to love highly cohesive, cross-functional on-site teams. These teams, much like monolithic applications; succeed due to the proximity of useful knowledge. Distributed Scrum teams must rely on different strategies and tactics in order to be effective while still adhering to the principles laid out in the Agile Manifesto.
If the basic principles of the Agile Manifesto and the Scrum framework are simple managing global Agile software development projects in the corporate world is sometimes more complex and complicated. This article lists some approaches that have been created to answers the specific questions raised by scaling Agile practices in large organizations.
How can metrics be used safely in coaching Agile teams? The classic Goldratt quote “Tell me how you will measure me and I will tell you how I’ll behave” signals the danger of using metrics to manage or motivate employees. This presentation shows and suggests approaches to Agile metrics that avoid the common pitfalls and shows some practical dashboards and the resulting chaos or calm they caused.
If agile started as a software development movement, the customer has been at the center of its values since its initial statement. The usage of agile and lean has now widespread beyond the IT world. In her book “Being Agile in Business”, Belinda Waldock explains the agile and lean approaches from a business perspective.
When I started with Agile and Scrum back at 2005, I was not much different from any other agile newbie, and I was complaining for having regular retrospective. “What for? We are already sitting together, we are a good team, we tell each other what should be said. It’s waste of time. Formal meeting…” Later I realized retrospective is quite useful and implemented it as one of the key Scrum practices.
Scrum Expert Copyright © 2009-2024 Martinig & Associates