Being brave is about doing what is necessary, even when you are afraid. The single most important thing in agile is to inspect and dare to change things which aren't working. You can start with small experiments to find solutions, and if it turns they do not work, then you can stop them.
Technology makes it easier to collaborate, but also distracts us and can have negative consequences on the quality and content of our personal interactions. The mere presence of a cell phone can pull you away from a task and reduce your focus. An interview with Jeffery Hackert on cultivating attention, awareness and empathy when working in teams, and giving and receiving uninterrupted attention.
Alexandre Magno, author of the book ”How Creative Workers Learn", gave a masterclass at the Scrum Gathering Portugal 2016 showing the power of the practices that emerge from the inside of an organization instead of being imported from the outside.
The latest edition of the Scrum Guide has been launched by Scrum co-creators Ken Schwaber and Jeff Sutherland. The biggest change in this version of the Guide is the inclusion of the Scrum Values.
Truly agile is what you are, and to become agile you need to overcome paradigms, argues Arie van Bennekum, co-author of the agile manifesto. It takes "being agile" and not "doing agile" to achieve success. Agile is an interaction concept based on the values and principles of the agile manifesto. Technology facilitates agile working, but tools don’t make you agile.
People can tell stories and express themselves when trying to solve complex problems using Lego. Jens Hoffmann facilitated the session "Prototyping an Agile Culture with LEGO® SERIOUS PLAY®" at the GOTO Berlin 2015 conference.
An interview with Nicole Forsgren about why organizations are starting to embrace DevOps methods, how being able to deploy fast can also increase IT stability, what to focus upon when changing the organizational culture to improve performance, how lean management can help to increase the performance, and asked her for advice when organizations want to apply DevOps to increase their performance.
Technology leaders are moving towards Continuous Delivery and Agile to accelerate business innovation.This post talks about the importance of cultural shift in successful Continuous Delivery implementation in the organizations.
An agile transformation needs a convincing involvement and statement by top management to show that the game really has changed says Jürgen Dittmar. InfoQ asked him about how management can be an obstacle in agile transformations, changing the mindset and approach for managing organizations, how managers and leaders can enable agility in organizations, and examples from applying Management 3.0.
The Agile New Zealand conference was held in Wellington, New Zealand last week. With over 350 conference attendees, four keynotes talks and 24 session the conference had an overall theme of Transformation and three tracks - Agile Transformation, Agile Enterprise and Digital Transformation. InfoQ attended the conference and there will be interviews and articles published in the next few months.
The volatility in the market requires that organizations become able to adapt to changing demand as fast as possible while gaining the highest value. To implement agile managers need to team up to remove impediments in the organization says Ahmet Akdag. An agility transformation is about learning to try, fail and learn.
At QCon London 2015, Helen Walton and Pete Burden came up with a discussion on the impact of culture in project’s success (failure indeed) and gave practical advice on how to influence the organization's culture to which a person is working for
When you want to scale agile you have to view it as “a way of doing things, a mindset and a culture for the whole company” says Christoph Mathis. To scale agile you need to change the culture to achieve a learning organization.
When an organization decides to adopt agile the way it is structured often has to change. An agile way of working also brings new practices for teams and managers, and usually impacts the culture and mindset. All of these are related, but changing everything at the same time might be a too big challenge for an organization. Let’s explore what can happen when we start with the structure.
Long working days, deadlines and team pressure can impact the quality of the software that agile teams deliver. What can we do to prevent that from happening and enable teams to improve the quality of their software? Some suggestions are to arrange for scope and deadline slack, adopt pull systems, and to make sure that people can slow down and get enough sleep.