InfoQ Homepage Scrum Content on InfoQ
-
/articles/kanbanace-improve-scrum/en/smallimage/logo-bridge.jpg)
Improving Scrum with the Kanban-Ace Framework
The Kanban-Ace Framework welcomes Scrum, and helps teams improve their level of agility. This article explores how a Scrum team can improve by leveraging the Kanban-Ace Framework. It introduces the Akashi Bridge, a new Kanban-Ace tool that makes it possible for Scrum teams to keep the best features of Scrum while growing to higher levels of performance thanks to Kanban-Ace advantages.
-
/articles/standardize-requirements-scrum/en/smallimage/logo-agile.jpg)
Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality. Without standardizing, the project may suffer. Standardizing requirements descriptions provides a minimum of eight benefits from requirements descriptions unification, which in turn positively affects testing and makes management of ongoing changes in requirements easier with the help of tools.
-
/articles/communities-of-practice-agile-organisation/en/smallimage/logo.jpg)
Communities of Practice: The Missing Piece of Your Agile Organisation
Communities of practice bring together people who share areas of interest or concerns. They have specific applications in agile organisations: scaling agile development and allowing individuals to connect with others who share similar concerns. Communities of practice bring people together to regain the benefits of regular contact while keeping the value of multidisciplinary agile teams.
-
/articles/how-make-agile-successful/en/smallimage/logo.jpg)
So, How Do You Make Agile Successful?
It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.
-
/articles/book-review-managing-happiness/en/smallimage/logo.jpg)
Q&A with Jurgen Appelo on Managing for Happiness
The book Managing for Happiness by Jurgen Appelo provides practices, games and tools to manage organizations and make work fun. It contains tips and suggestions for applying the practices to achieve organizational greatness and maximize learning in organizations.
-
/articles/break-silos-ventilators/en/smallimage/LOGO.jpg)
Don't Break Your Silos - Push Out the Silo Mentality
Organizational silos are a serious hurdle for many companies out there. They may cause a wide variety of problems if not dealt with accordingly. Silos may not need to be broken if you manage to push out the mentality that comes with them by creating ventilators. The first step towards dealing with the silos is to learn more about them and familiarize yourself with the best practices against them.
-
/articles/product-development-mechanisms/en/smallimage/logo.jpg)
Product Development Mechanisms
Steve Andrews discuses the need to empower self-managing teams to stay focused on delivering high-quality solutions using mechanisms like tenets and exit criteria.
-
/articles/book-review-pichler-strategize/en/smallimage/strategize-100dpi.jpg)
Q&A with Roman Pichler about Strategize
The book Strategize by Roman Pichler provides practices, advice, and examples for product strategy and roadmapping that you can use to create successful products. InfoQ interviewed Pichler about applying product strategy and roadmapping with agile, innovation in product strategy, eliminating features when defining products, different kinds of roadmaps, and measurements for product management.
-
/articles/user-stories-placeholders-requirements/en/smallimage/agile-logo.jpg)
User Stories Are Placeholders for Requirements
It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.
-
/articles/agile-jedi-scrum/en/smallimage/logo.jpg)
Going Through the Scrum Motions as Opposed to Being an Agile Jedi
The force awakens: is it Agile or are we just going through Scrum motions? Michael Nir speaker and Agile coach shares expert best practices; too much Scrum might lead us to the dark side of the force. Being Agile rather than doing Scrum – focus on what we want to achieve; getting the right products that our users want quickly, using fast feedback loops, and employing continuous removal of waste.
-
/articles/strategy-handling-defects/en/smallimage/agile-logo.jpg)
Now or Never: the Ultimate Strategy for Handling Defects
How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.
-
/articles/dave-snowden-leadership-cynefin-requirements/en/smallimage/logo.jpg)
Q&A with Dave Snowden on Leadership and Using Cynefin for Capturing Requirements
Dave Snowden gave a talk titled "Context is Everything" at the Scaling Agile for the Enterprise 2016 congress in Brussels, Belgium. InfoQ interviewed him about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.