InfoQ Homepage Assessment Content on InfoQ
-
Leadership Principles for Agile Organizations
Selena Delesie gave a keynote at the Agile Testing Days 2015 about leadership principles that she sees in successful agile companies. InfoQ interviewed her about how leadership principles from Sir Richard Branson are related to the foundations of agile and asked her which principles are giving companies a competitive edge and how companies can deploy agile to become more competitive.
-
Role of Autonomy in Agility
Autonomy is one of the core guiding principles at Spotify. It enables employees to make decisions as close to the works that is being done as possible. At the Agile Greece Summit 2015 Kristian Lindwall and Cliff Hazell from Spotify explained why autonomy is at the heart of agility.
-
Agile and Lean Adoption in Greece
Small and medium sized companies have adopted the agile way of working in Greece and there are few examples of agile in larger organizations, interest in agile from the local industry is growing. Among the topic discussed in agile meetups are whether companies should implement Scrum or Kanban, Scrum for startups, dealing with fixed price and scope contracts, productivity, and happiness in teams.
-
How to Facilitate an Agile Retrospective Using "Rory Story Cubes"
How to use Rory Story Cubes for sprint retrospective.
-
Anti-patterns for Handling Failure
Oliver Hankeln shares the anti-patterns he found for handling failure in organizations: hiding mistakes, engaging in blame game, the arc of escalation and cowardice. He then suggests corrective actions for each of them.
-
Importance of Courageous Communicators in Agile Organizations
It is very important to have courageous communicators in agile teams. Senior leadership should support the role of courageous communicators.
-
Limitations of the Five Whys Technique in Agile Retrospectives
This post includes the limitations of Five Whys technique.
-
Step by Step Improvement Needs Relative Safety
At the OOP 2015 conference Colin Hood talked about bridging the gap between requirements engineering process definition and successful iterative roll-out. He presented how the introduction of improvements to requirements engineering can be done better when done step by step, and how relative safety is needed to enable people to take the steps.
-
How To Get a Happier Workforce
Laughing can help to create a better team climate which can lead to better results. There is compelling evidence that happiness and positivity can lead to success. Here are some suggestions for what you can do when you want to improve happiness in teams.
-
Feedback Cycles in Scrum
In agile software development feedback plays an important role. Many are aware how feedback supports dealing with changing requirements and adjusting the way of working in teams with retrospectives. But there is more that feedback can do in agile. “An effective feedback cycle in Scrum is more than having sprints and doing retrospectives” says Kris Philippaerts.
-
Q&A with Andreas Schliep on ScALeD – Scaled Agile and Lean Development
The introduction and integration of agile approaches to an organization should be regarded and treated as an agile project itself says Andreas Schliep. An interview with Andreas about pitfalls when trying to scale agile, on ScALeD and how it compares to Agility Path, LeSS, SAFe and DaD, and on continuous improvement and scaling retrospectives.
-
Why Pair Programming is Hard to Implement
Pair Programming is good for increasing the software quality and collaboration within team members but it is hard to implement. This news describes the reasons why it is hard and how to figure out good practices of pair programming for your team.
-
Emotion Cards for Agile Teams
This news describes usage of emotion cards as an effective tool in the toolbox of any scrum master, agile Coach or trainer. Emotion Cards are a set of cards showing common emotions like angry, anxious, confused, happy, sad, surprised, tired and worried.
-
Huge Retrospectives with Online Games
Agile retrospectives are mostly done at the team level or at a project level. What if you need to conduct a retrospective with 50 teams or more? Luke Hohmann describes how a large scale agile transformation project did a huge retrospective to create insight on what was going well and what needed to be improved.
-
Fail Fast Means Learn Fast
Failing fast and often is one of the encouraged practices for agile teams. Sander Hoogendoorn, author of the This is Agile book discusses on his blog the importance of having a strategy that helps you on the decision of aborting a project by assuming its failure on an early stage.