InfoQ Homepage Adopting Agile Content on InfoQ
-
/articles/network-gateway-less/en/smallimage/logo-agile1.jpg)
Developing a High Capacity Network Gateway with LeSS
This report summarizes how the Large-Scale Scrum (LeSS) framework was used in developing a high capacity network gateway and how to grow R&D from 2 co-located teams to 20+ teams. It also describes how LeSS and agile development practices significantly accelerated the time to market and gave us the flexibility that traditional development practices never offered.
-
/articles/agile-non-it/en/smallimage/logo2.jpg)
Implementing Agile Delivery for Non-Software IT Projects
Most organizations avoid using Agile for IT projects that do not involve software delivery (e.g. roadmap planning and architecture development). These projects deliver high value, but are often the most risky of all projects - and high risk demands Agile delivery. This paper discusses how Agile can be successfully adopted to deliver these projects by going back to the basics of Agile philosophy.
-
/articles/book-nature-of-software-development/en/smallimage/cover2.jpg)
Q&A with Ron Jeffries on The Nature of Software Development.
The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development. It's a book of questions, not of answers, says author Ron Jeffries, for readers to discover the natural way to develop software, the simple way, inside themselves.
-
/articles/project-to-product-agfa-less/en/smallimage/logo3.jpg)
From a Project to a Product Approach Using LeSS at Agfa Healthcare
By changing the inner workings from a project perspective to a product perspective Agfa Healthcare established a less complicated process using a single backlog for the entire organisation. Main advice is to try to avoid setting up silos where they do not belong. When applying LeSS it is important to stick to its basic rules even though they are, in most organisations, very disruptive.
-
/articles/agile-input-management/en/smallimage/LOGO.png)
An Agile Input Management Process Framework - The Agile IMP
Agile methods and processes such as Scrum give us conceptual tools to implement our innovative ideas. But that toolset seems to miss a crucial part: A well-structured ideas development process. The Agile IMP (Input Management Process) proposes a conceptual framework for managing input from multiple sources, for maturing input and for basing product decisions on soundly evaluated propositions.
-
/articles/pitfalls-avoid-agile/en/smallimage/logo.jpg)
The Pitfalls that You Should Always Avoid when Implementing Agile
Moving from traditional project management to agile is a paradigm shift. From push to pull systems from a control-and-command culture to a trust culture where authority is delegated. A good structure with some control mechanisms will most likely help you get the wanted results quicker. This article discusses the role that management plays in organizations that have decided to adopt agile.
-
/articles/blockers-defects-process-improvement/en/smallimage/article-logo2.jpg)
Using Blocker Clustering, Defect Clustering, and Prioritization for Process Improvement
When work gets delayed (it’s blocked), it is of particular interest to look for ways to improve the smooth flow of work by resolving the causes of that delay. In the long term, finding ways to eliminate the root causes of these delays is a superior solution. This article discusses clustering blockers and provides ways to prioritize those blockers that have the most impact or are the quickest wins.
-
/articles/essence-flow/en/smallimage/logo.jpg)
The Essence of Flow
How do you get good flow? A common scenario in a software company is that too much is going on at once. We need a shift in mindset, to go from focus on resource efficiency to focus on flow efficiency. This article presents concrete examples on how to achieve flow by limiting WIP, reduce wait times and arrange cross-functional teams.
-
/articles/flow-manager-deliver-fast-smooth/en/smallimage/artlogo.jpg)
How a Flow Manager Helps Teams Deliver, Fast and Smoothly
As agile software delivery practices and management evolve, so, too, do the roles. kanban has introduced the idea of managing flow, one of the method’s core practices. With talented developers, quality advocates and user-experience designers, teams know how to deliver valuable software. But as we improve service delivery using kanban, who manages flow?
-
/articles/change-practices-principles-values/en/smallimage/agile-logo.png)
Why We Fail to Change: Understanding Practices, Principles, and Values Is a Solution
There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We see virtually no impact of agile or lean on the bottom line of success rates of improvement initiatives, because organizations often look for recipes. We need to change our mindset, and focus on the principles that people follow and values they share and the bigger whole: organizational culture.
-
/articles/experiments-data-innovation/en/smallimage/logo-agile.jpg)
Using Experiments and Data to Innovate and Build Products Customers Actually Use
An interview with Jan Bosch, professor of software engineering and director of the Software Center at Chalmers University of Technology, about the benefits that companies can get from increasing delivery speed, the next steps that organisations can take after adopting Agile and DevOps, using experiments to innovate, practices for experimentation and how organisations can become more innovative.
-
/articles/book-the-scrum-culture/en/smallimage/9783319118260.jpg)
Q and A on The Scrum Culture
Dominik Maximini researched the cultural aspects of organizations that are using Scrum. He published the findings of his research, together with principles for implementing Scrum and suggestions on how to apply these principles and a case study of a Scrum transformation, in the book The Scrum Culture.