A lot of the pain that large and medium-sized organizations are facing boils down to scaling. It is not difficult to have 5-10 people working together in one room. However, as your business becomes more successful and your hiring increases, you will start to see problems. At Jimdo, the approach to scaling relies on three major factors: culture, communication, and kaizen.
Self-organized teams manage their work, the processes that they use and the way that they work together as a team and with their stakeholders. Robert Pankowecki is writing a book on Developers Oriented Project Management which aims to help programmers, product owners, project managers and agile company owners to improve their project management practices and move towards more flat organizations.
Why do we promise more than we can deliver? Why do we say yes when we are already too busy? Chronic Overcommitment is a pervasive problem in the IT industry. In this article we take a look at the behaviors that drive over commitment and the dynamics at play in your organization the make it a difficult problem to solve. Finally, we offer some advice to those who suffer from this affliction.
Some 80% of all improvement and change programmes fail. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.
Developers hate writing down anything that isn’t code. But there are times on a project when a little documentation can go a long way. In this article, we discuss when and why to write things down. 5
InfoQ have talked to Dan North, Gojko Adzic, Elizabeth Keogh and Matt Wynne about Specification by Example, Executable Specifications and Feature Injection and how they relate to BDD. 1
Ken Howard and Barry Rogers have written a book that focuses on the first value from the Agile Manifesto. They provide advice, tools and techniques to help teams and individuals improve interactions. 2
In this article, excerpted from the book Coaching Agile Teams, Lyssa Adkins shows you how to activate the journey toward high performance in an Agile team in both provocative and practical ways.
This article by Andres Kutt summarizes six learnings from 55 months as an architecture team lead at Skype. Some of them are technical while some focus upon the softer aspects of an architect's work. 20
This article shows how flirting skills can be used to improve interactions in the workplace. 13
One of the responsibilities of self-organizing teams is to take decisions that respect everyone’s opinion. This book has some examples in coaching the team to navigate through difficult discussions.
Reuse can be hard, especially in a large organization. Vijay Narayanan offers 10 practical tips to assure effective reuse of software components. 4