I’ve been working with teams who want to move to agile. Some people on their teams are in another location, where the salaries are cheaper. It’s difficult to get agile started with a geographically distributed team. If everyone’s distributed, it’s easier than if just some people–especially if they are all one function, such as developers […]
One of the problems many people encounter when moving to agile is that they (literally) cannot imagine iterations shorter than 4 weeks. I rarely recommend an iteration as long as 4 weeks now, and if people insist on 3 weeks, suggest they find the root cause for the reason their iteration needs to be so
Wow! I can hardly believe how many people have signed up for the brand-new free teleclass, “3 Crucial Factors For Preventing Your Agile Titanic” that Gil Broza and I will be teaching next week! I guess we struck a nerve with many people who want (or need) to get Agile going, and who don’t have
Dave and Bob have great comments on my post, Might Three Backlogs Be Better Than One?. Dave is describing situations where management is making reasonable decisions, not incurring management debt, and by extension, technical debt. Bob and I have experience with significant management debt. (Take a look at Musings About Management Debt for more information
I’ve been working with several clients on their transition to agile approaches to their projects. They all have a common state: Many features to implement Huge technical debt Many defects They want to get a handle on all the work they have to do. I suggested they consider three backlogs, making sure that for a
In their comments to my post, Agile and Remote People: Part 1, Telecommuting, Matt, Lisa, Pete, Abby all had great rebuttals. They successfully make their remote teams work. They have successfully built trust. They use a variety of communications tools that allow their team members to work together. Good for them. (I mean it. I am
A twitter follower was concerned with a piece of my post, Do What’s Effective For You, when I spoke of team bits. Was I saying you could not telecommute and do agile? First, let me explain what a team bit is. A team bit is a person or a group of people grouped by geography
At a prospective client, a senior manager asked me, “In agile, when does the spec freeze?” I said it either didn’t, or did at the end of any iteration in which people wrote a spec. He had a puzzled look on his face, so I explained that if you discuss how to design or what
I’m a member of a panel Jul 23 for the Boston Agile Bazaar meeting, and am attempting to articulate my two-minute position statement to the question: How would you characterize your approach to handling people problems on agile teams? My problem is that I don’t do anything any differently for agile or non-agile teams. I
In the Small Steps and Plunge In posts, I said projects should transition to agile all the way. But does it work the same way for the entire organization? Nope. I recommend a gradual approach to moving to agile. Not all project teams are ready for the self-discipline agile requires. But, even more importantly, too