InfoQ Homepage Distributed Team Content on InfoQ

Articles

RSS Feed

Newer Older

Q&A with Robert Pankowecki on his book Developers Oriented Project Management

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.

Ben Linders
on Apr 10, 2014
Remote Working Works

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.

Tom Howlett
on Mar 24, 2014
Solving the Gordian Knot of Chronic Overcommittment in Development 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.

Morgan Ahlström Rolf Häsänen
on Feb 13, 2014
Intelligent Evolution: Making Change Work

Some 80% of all improvement and change programmes fail: they did not achieve the expected results, the investment in the change programme was greater than the value achieved, “improvements” were seen as mostly bureaucratic, or changes were abandoned soon after the implementation. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.

Peter Leeson
on Jan 13, 2014
I’d Rather Be Coding – Writing Things Down

For lots of reasons, most developers hate writing down anything that isn’t code. The Agile Manifesto deemphasizes documentation, but there are times on a project when a little documentation can go a long way. In this article, we will explore why collaboration over comprehensive documentation shouldn’t mean “NO” documentation – and when you should stop coding and start writing things down.

Nate McKie
on Dec 31, 2013
Agile Walls

BVCs, TOWs and POWs are very important tools in the agile world but what exactly are they? BVCs are Big Visible Charts, TOWs are Things on Walls and POWs are Plain Old Whiteboards – information radiators all. Using the right wallware and the information they provide can make or break an agile team.

Sharon Robson
on Dec 14, 2013
Agile Fluency: Finding Agile That's Fit-for-Purpose

The Agile Fluency model is a way of thinking about and planning investments to create the conditions of Agile that best fit your development effort, business need, and customer value. James Shore and Diana Larsen described it in the 2012 article "Your Path through Agile Fluency". This article by Diana aims to helps you to use the Agile Fluency model effectively.

Diana Larsen
on Nov 12, 2013
Experiments in Performance Management to foster High Performing Agile Teams

Experiments in Performance Management to foster High Performing Agile Teams: A question that often comes up – Agile talks about team performance so why am I measured on individual goals which have little to do with team performance? The author discusses some approaches which can bridge the gaps between performance management and team productivity.

Kamal Manglani
on Sep 13, 2013
How To Not Destroy your Agile Team with Metrics

The agile community needs to change how it measures success. The ways that we gather metrics and the information we seek out of those metrics is actually getting in the way of what’s most important, making working software. Forcing individual metrics sometimes discourages team collaboration by focusing too intently on others. This can skew the thing we’re measuring, thus defeating the purpose.

Sean McHugh
on Oct 22, 2012
STEP – A Map for an Agile Journey

Are you finding joy in work and delighting your customers? STEP is simple map for an Agile-inspired journey of continuous improvement. Start by Stopping to visualize your work-flow. Transform your way of work, limiting the amount of work-in-process. Then Expand your improvements, inspire more people to develop the habit of team learning. Finally, keep walking, keep Perfecting your way of work.

Horia Slușanschi
on Aug 14, 2012
Culture & Methods

My Experience as a QA in Scrum

The QA role in Scrum is much more than just writing test cases and reporting bugs. In this article, Priyanka Hasija shares her experiences and the valuable lessons learned over the past 2 years while serving as a QA analyst on a Scrum team. She explains how QAs not only perform agile tests but also fill many other roles and responsibilities, earning them a place of importance on the team.

Priyanka Hasija
on Jul 17, 2012
Lessons From A DevOps Journey

Matt Callanan has been pushing the boundaries of Agile software development for over six years and most recently he extended that journey to DevOps. He recently shared his experiences in a talk at the Agile Development Practices West conference entitled "Lessons From A DevOps Journey". InfoQ caught up with Matt prior to the conference to find out more about his experiences in DevOps.

Craig Smith
on Jun 27, 2012

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles