Example 2: Using a Project Manager with Kanban, Silo’d Teams This is a product development organization with developers in Italy, testers in India, more developers in New York, product owners and project managers in California. This organization first tried iterations, but the team could never get to done. The problem was that the stories were […]
I’ve been working with geographically distributed and dispersed teams for the past couple of years. Some of them on quite large programs, some of them reasonably small. What they all have in common is that they all want to transition to agile. Most of them start this way: someone takes a Scrum class, gets all
I’m so pleased to announce that Shane Hastie and I are leading a workshop on Working Effectively In Geographically Distributed Agile Project Teams, April 17-18, 2012 in Pleasanton, CA. Yes, that is Elisabeth Hendrickson’s Agilistry Studio. Shane and I first delivered this workshop last year in Australia, when I was there for Software Education‘s SDC.
A Workshop with Johanna Rothman and Shane Hastie, Pleasanton, CA, April 17-18, 2012. Geographically distributed projects are a reality in many organisations today; teams spread across multiple locations – diverse cities, states, countries, cultures and time zones. How can you work effectively in a geographically distributed agile team? Can a distributed team really go agile?
I have posted last week’s Pragmatic Manager, Are You Being Guilted Into Doing More?. At Agile 2011, I had a great video conversation with Shane Hastie about agile project portfolio management. The chair is big, I’m not so short. The chair is big, I’m not so short. How many times do you think I have
I posted my most recent Pragmatic Manager: Are Your “Shoulds” Driving Your Decisions? Yes, in case you couldn’t tell, I am doing a series on project portfolio management, so that you do take a look at my Peer Project Portfolio Coaching. Several people took advantage of the early bird pricing. We’re in the not-quite-early-bird pricing
I have an article posted at Techwell, Management Myth #1: The Myth of 100% Utilization. This myth has always been a problem. It’s even more of a problem now as more organizations transition to agile. People need time to think. They need time to adapt to their current circumstances. They need time to create their
If you missed my most recent Pragmatic Manager newsletter, Focus on One Thing at a Time, it’s posted. In it, I ranted about the delays of multitasking and introduced a new service: Peer Project Portfolio Coaching. I keep seeing people trying to make the transition to agile, still multitasking and not able to say No
A manager took me aside at a recent engagement. “You know, Johanna, there’s something I just don’t understand about this agile thing. It sure doesn’t look like everyone is being used at 100 percent.” “And what if they aren’t being used at 100 percent? Is that a problem for you?” “Heck, yes. I’m paying their
I’ve been working with folks making their transition to agile. One of the hardest transitions is for the managers and technical leaders. Managers are accustomed to working in timeboxes. To them, the iteration is a timebox. But, they also are accustomed to features spanning multiple timeboxes, and that’s not OK in agile. They are accustomed