Retrospectives help teams to learn from their experiences and improve continuously. In this interview Nadja Macht, Flow Manager and Coach at Jimdo, talks about how to balance flow and slack time in teams, doing visual management with Kanban boards and deploying agile retrospectives for continuous improvement.
Do you assume that remote working is a compromise? Around 5 years ago my team, and much of our software house, decided we could work as effectively from home. Many of us left London and headed to the country, replacing bars and restaurants with poultry keeping and mountain biking. Today we are closer, collaborate more, recruit better people and work more effectively than we ever did.
Agile adoption is struggling - organisations mandate agile practices expecting teams to change their way of working but the changes don't seem to be sustainable. This is the second in a series of articles which examine why this is happening and suggest an alternate approach - Open Agile adoption based on invitation and engagement rather than mandate and instruction from above
Agile and offshore development are critical success factors for many organizations, but have never worked well together. The “Design for Hybrid Agile Adoption (DH2A)” methodology offers a solution. 3
In this interview, Ben Linders explores with author William E. Perry his motivation for writing the book iTeams – Putting the “I” Back Into Team and the challenges teams face and learn to deal with.
Key to the success of Agile is a "Whole Team", a cross functional team of generalizing specialists. A group that works across boundaries. Matthew Philip diagnoses some of their common problems. 2
We examine the compatibility between SOA and Agile development.
The main takeway points and lessons learned from QCon San Francisco 2008 as seen by the many attendees who blogged about QCon. Experience QCon through the opinions of the attendees!
Dr. Linda Rising talks about experiments conducted many years ago, presenting how deep, powerfully affecting, and difficult to avoid are human “prejudices” and “stereotypes”. 1
Developers and the business use numbers differently, leading to poor communication. Here the "Spirit of Agile" tells a developer the trick: translate non-computational issues into number language. 3
The main takeway points and lessons learned from QCon London 2008 as seen by the many attendees who blogged about QCon. Experience QCon through the opinions of the attendees!
The main takeway points and lessons learned from QCon San Francisco 2007 as seen by the many attendees who blogged about QCon. Experience QCon through the opinions of the attendees! 2