InfoQ Homepage Agile Conferences Content on InfoQ
-
Retrospectives for Management Teams
Engaging top management in a recurring retrospective approach can result in long-term value in organizations. Retrospectives can help management teams to explore how they collaborate and cooperate. They can find out whether they should change something and decide on action points that propel the team forward and make them more effective.
-
Innovation Startups Modeling Agile Culture
Innovation is not only about the most advanced technology; management and processes are the new era of startups' innovation. To mix the power of the data and the importance of people to offer business intelligence is a key point nowadays. The result is not only the most important thing; the way you do it is more important. To be agile is to adapt to today's market.
-
Software Teams and Teamwork Trends Report Q1 2020
The Culture & Methods editors team present their take on the topics that are at the front of the technology adoption curve: how to make teams and teamwork more effective, in person or remote, some new tools and techniques, some ideas that have been around for a while and are starting to gain traction, the push for professionalism, ethical behavior and being socially and environmentally aware.
-
Using OKRs to Build Autonomous Impact Teams
To focus on outcomes rather than outputs, Meilleurs Agents uses the Objective and Key Results framework to align the whole company on what they want to achieve. Christopher Parola and Nicolas Baron gave a presentation at FlowCon France 2019 where they showed how they implemented the OKR method and turned their product and tech teams into impact teams.
-
How King uses AI to test Candy Crush Saga
To be able to improve features in games which are constantly evolving, the challenge will be to scale tests to be on a par with new feature development. Automated tests are vital for King to keep up testing Candy Crush, therefore they are constantly looking for new improved ways to test.
-
A Transformation Journey for a Distributed Development Organization
Agile transformations are never easy, but are even more challenging than usual when it comes to geographically distributed teams. This article highlights experiences from Konica Minolta’s Workplace Hub program and shares the methods that helped them on their journey. It's about the organization, processes, but most importantly, about the people and the mindset.
-
How SwissLife France’s Enterprise Architects Used Lean to Raise Their Level of Influence
This article shows how Lean has been successfully applied to its own activities by an Enterprise Architecture team. Making the flow visible, loving problems and having fun solving them, and welcoming voice of the customer feedback were some of the practices that helped the team navigate the flow. Lean allowed them to better live to their purpose, both individually and as a team.
-
The Evolution of Lean Thinking - Transitioning from Lean Thinking to FLOW Thinking
The Flow System provides a re-imagined system for organizations to understand complexity, embrace teamwork, and autonomous team-based leadership structures. It is a holistic FLOW-based approach to delivering Customer 1st Value. It is built on a foundation of TPS and LEAN, plus a new triple helix structure known as the DNA of Organizations.
-
Using Kanban with Overbård to Manage Development of Red Hat JBoss EAP
As planning the work for Red Hat JBoss EAP became harder and harder, Red Hat decided to adopt Kanban to make their development process more manageable, while maintaining a very high level of quality. They introduced Kanban in their distributed team and developed their own Jira add-on for visualizing the work, and added parallel tasks to their Kanban cards to simplify the workflow.
-
Lessons Learned in Performance Testing
Performance testing is a hard discipline to get right and many things can go wrong. The key is to pay attention to the details, understand the behavior, and avoid just producing fancy numbers. This article describes a few common problems seen frequently with performance testing and shares tips on how to make your performance testing routine better.
-
Psychological Safety: Models and Experiences
This paper discusses psychological safety that refers to a climate in which people are comfortable being (and expressing) themselves. A proposed model (called S.A.F.E.T.Y.) is discussed briefly, and the article proposes a path to how we can use this model in agile adoptions related to teams and organizations.
-
Velocity and Better Metrics: Q&A with Doc Norton
Velocity is not good for predictions or diagnostics, argued Doc Norton at Experience Agile 2019. It's a lagging indicator of a complex system which is too volatile to know what our future performance will be; it isn’t stable enough to be used reliably. We can use Monte Carlo simulation for forecasting, and cumulative flow diagrams to track work, see changes in scope, and spot bottlenecks.