Shane and I recorded a webinar at noon today, about our Geographically Distributed Agile Teams workshop. We had a great time, and answered a lot of questions. We had a few recording glitches, so if you hear me talking over Shane, oops. To me, it sounded as if he was not talking. There is a […]
Simone, a French project manager, emailed me. “Johanna, we are having trouble getting the people together. These people worked together before on the previous release. But on this release, they are not working together. I’ve done these things,” and she listed a number of smart ideas. I replied by email, “Where’s the project charter with
I hope that by now you see that you have any number of choices for your lifecycle if you are geographically distributed team and you are transitioning to agile. I do recommend a servant leader agile project manager, for coordination and risk management. With people all over the world, it’s difficult to coordinate the project,
Example 3: Using a Project Manager with Iterations and Kanban and Silo’d Teams Here, the developers were in Cambridge, MA, the product owners were in San Francisco, the testers were in Bangalore, and the project manager was always flying somewhere, because the project manager was shared among several projects. The developers knew about timeboxed iterations,
A reader asked why the lifecycle in Agile Lifecycles for Geographically Distributed Teams, Part 1 is not Scrum. It’s not Scrum for these reasons: The project manager and product owner start the release planning and ask the team if the release planning is ok. The team does not generate the initial draft of release planning
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’ve been blogging about agile architecture, and the responses have been fascinating. Some people are totally against the idea of an agile architect, regardless of the size of the program. Others are ready to give me the benefit of the doubt. In this column, let me clarify the case for (or against) the job-titled agile