InfoQ Homepage Culture & Methods Content on InfoQ
-
Q&A on Fifty Quick Ideas to Improve Your Tests
An interview with Gojko Adzic, David Evans and Tom Roden on why they wrote this book, how quantifying quality can support testing, balancing trust levels when testing large and complex systems, why automating manual tests is almost always a bad idea, on using production metrics in testing, how to reduce or prevent duplication in test code, and on upcoming books in the fifty quick ideas series.
-
Probabilistic Project Planning Using Little’s Law
When working on projects, it is most of the time necessary to forecast the project delivery time up front. Little’s Law can help any team that uses user stories for planning and tracking project execution no matter what development process it uses. We use a project buffer to manage the inherent uncertainty associated with planning and executing a fixed-bid project and protect its delivery date.
-
Q&A with Dean Leffingwell on Leading SAFe LiveLessons
Dean Leffingwell’s “Leading SAFe LiveLessons” - training videos are based on Lean-Agile transformation concepts at enterprise level. The Scaled Agile Framework (SAFe) provides practices, roles, activities and artifacts for applying Lean and Agile development at enterprise scale.
-
Q&A on Test Driven Development and Code Smells with James Grenning
InfoQ interviewed James Grenning about why people are not doing technical practices sufficiently or well enough, why he thinks that TDD can be fun, the importance of unit tests, why programmers need to have a good nose for code smells and how they can become better in discovering "bad code”.
-
The Cloud Migration Checklist
Are you in the process of moving applications to a public cloud? You’re not alone. 451 Research says that 46% of 2015 IT budgets are going towards off-premises systems, with that number expected to climb to over 50% within the next three years. In this article, we’ll explore four stages in a cloud migration lifecycle and the questions to answer before exiting each one.
-
Using Large-Scale Scrum (LeSS) with Feature Teams to Ship Your Product Every Sprint
An interview with Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility. Larman also explained how organizations can work with feature teams, and gave examples of how teams and stakeholders can be in direct contact with their customers and users and can work together to ship their product every sprint.
-
Q&A with Claudio Perrone on PopcornFlow / Evolve and Disrupt
At the Agile Eastern Europe 2015 conference Claudio Perrone gave a keynote titled "Evolve and Disrupt". InfoQ interviewed Perrone about continuous evolution, servant leadership, popcorn flow (an approach to continuous evolution through rapid experimentation), and doing experiments to make change more continuous.
-
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.
-
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.
-
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?
-
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.
-
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.