Software development can be viewed as collaborative knowledge work. Such a view calls for different ways to manage organizations and the people who work in it. Bob Marshall wrote several blog posts about the antimatter principle. InfoQ interviewed him about this principle and the practices to use it to attend to the needs of people.
Adopting agile is an organization change which involves management. It is said that management buy-in is crucial for agile to succeed and that a lack of management support can be a barrier in agile transformations. There are different ways for management to support agile in enterprises.
Kanban helps organizations to get insight into their work-in-progress, and establish a pull system where demand and capability can be balanced. A first step is to find out what the real capability is and visualize the flow. InfoQ interviewed Florian Eisenberg about evolutionary change and how you can balance demand and capability in organizations.
Agile is about a mindset and a contiguous improvement of everything said Yves Hanoulle. InfoQ did an interview with him about the habits that people have and what you can do to get into the habit of improving.
The 2013 international conference in Central Europe about Lean and Kanban (LKCE13) included presentations about change management, systems thinking, leadership, learning, and teamwork, and case studies from larger organizations that have applied Lean and Kanban. InfoQ interviewed Arne Roock about deployment of Lean and Kanban in agile software development.
How can you combine Scrum with a project constrained by a fixed price and completion date? Tim van Baarsen discusses his experience of completing a fixed-everything tender through continuing to work with Scrum behind the scenes.
Having stable teams can be beneficial for agile software development. Several views on establishing and nurturing stable teams, and dealing with team dysfunctions.
Two video lessons covering agile coaching and organizational change were released by Pearson/Addison-Wesley in the last quarter of 2012. They provide a different way to increase knowledge on agile adoption for visual and audible learners.
A recent article by Bob Marshall in Business Technology takes a look at how to change people’s behavior in organizations, by addressing the environment in which they do their work.
The 10th anniversary edition of the XP Days Benelux 2012 conference provides good opportunity for exchanging ideas and sharing experiences on agile. An impression of some of the sessions from day 1.
How do you work with difficult and uncooperative people? People who are combative or unprofessional? People who seem actively opposed to the agenda?
Trying to Sell Scrum to Management? Failing and wondering why? This often happens in the days after someone returns from a CSM course ready to help change the world.
Part of Project Coin is the ability to deal with Automatic Resource Management, or simply ARM. The purpose is to make it easier to work with external resources which need to be disposed or closed in case of errors or successful completion of a code block. An initial implementation is now available in OpenJDK.
A key decision for software architects involves where and how to introduce change into a system in order to effect a desired change. Leverage points are those places where micro changes can result in macro results. Twelve categories of leverage point are identified along with concerns about the changes.
It was recently announced that InfoQ is creating a new Operations community. In addition to that, another major change which has been in the works for the last few months at InfoQ is the conversion of the Java community to the Scala community. InfoQ spoke with a prominent Scala expert and members of the former InfoQ Java editorial team to learn more about this change and why it was made.