BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Scrum Content on InfoQ

  • Better Scrum through Essence

    Scrum is easy to explain and hard to do well. The majority of Scrum Teams struggle to do Scrum well. The OMG Essence standard promises to make practices more accessible and to free them from the tyranny of formal methods and frameworks. This article explains how Essence Scrum practices produced by Ian Spence and Dr Jeff Sutherland can help your teams get better at Scrum regardless of the context.

  • Speed, Efficiency, and Value: Using Empiricism to Achieve Business Agility

    Customers seek solutions that improve their outcomes, and organizations don’t know what will achieve this until they deliver something to them, measure the results, and adapt accordingly. Doing so repeatedly, frequently, and with the smallest investment to achieve the greatest amount of feedback, is the essence of organizational agility. This is key to success in today's complex world.

  • How to Decide in Self-Managed Projects - a Lean Approach to Governance

    Whether self-managed or self-governed as a project, the power still needs to be distributed internally. If the project is open to decide how things are done, how do we decide? A solid but flexible set of tools and practices like sociocracy is a great starting point for projects to have clear but lean processes that can grow as we grow.

  • Resetting a Struggling Scrum Team Using Sprint 0

    Sprint 0 can be a great mechanism in Agile transformations to reset existing teams which are not delivering value, exhibiting a lack of accountability, or struggling with direct collaboration with customers. This article shares the experiences from doing a Sprint 0 with an existing team which was struggling to deliver, helping them to align to a new product vision and become a stronger team.

  • Seven Key Insights of Product Management

    What a product manager does and how they do it seems like a perennial question, an ongoing discussion, often ending in debate. This changes depending on factors such as the size and culture of the company, the industry or sector, the business model, where the product is in its lifecycle, and the type of product. What doesn’t change is they’re always thinking about customer and business needs.

  • Augmenting Organizational Agility Through Learnability Quotient (LQ) - an Architect’s Perspective

    By creating a robust learning framework for the organization, and involving architects and other key technical leaders, Halodoc improved their organizational agility.

  • Applying Lean Tools and Techniques to Scrum

    This article focuses on some of the challenges that Scrum is facing and how Lean can be a complementary approach. Lean is often misunderstood as a heavyweight process when in fact it is a philosophy, one that is grounded in continuous improvement. The topic of waste, a central theme that Lean helps focus on, shows us that Scrum can be improved upon.

  • Reawakening Agile with OKRs?

    Corporate agile often represents an improvement over what went before but falls short on delivering the high performance management wants and quality engineering environment developers dream of. The backlog becomes tyranny. Could OKRs - objectives and key results - reawaken the radical side of agile? Or do OKRs represent a return to command and control?

  • ‘Debt’ as a Guide on the Agile Journey: Organizational Debt

    In this article in a series on how ‘debt’ can be used to guide an agile journey, we will provide two examples of smells that are related to organizational debt, explain the symptoms, the impact on the business and in our organization, outline the experiments (countermeasures) that we have introduced in an effort to try to remove the smell, and provide some specific advice for you to be inspired.

  • Surviving Zombie Scrum

    The book Zombie Scrum Survival Guide by Christiaan Verwijs, Johannes Schartau, and Barry Overeem aims to support teams that are stuck in Zombie Scrum. It helps them to understand why things are the way they are and provide them with experiments to get out of this state of Zombie Scrum by enabling collaboration with stakeholders, working increments, autonomy for teams, and continuous improvement.

  • Software Systems Need Skin in the Game

    Consequential decisions need to be taken by the people who pay for the consequences, by the people with skin in the game, and modern software practices need to reinforce this idea. On-call engineering is the quintessential modern engineering practice to create skin in the software development game.

  • Who is on the Team?

    Ahmad Fahmy and Cesario Ramos take the changes to the new Scrum Guide as an opportunity to explore what it means to be "on a team." They draw on research to create an ACID test to differentiate who is on the team and who isn't. They discuss different mental models around the idea of a team with the hopes that you take this opportunity to discuss and elevate the roles within your organization.

BT