MPD

Books, MPD

Pairing Improves Writing

I’m writing a geographically distributed agile team book with Mark Kilby. We have a 30-minute timebox each morning to write. (We take time off for holidays, vacations, travel, etc.) Because we’re writing together, we first had to understand what we wanted to write in this book. We created a frame and a story map for […]

MPD, podcast

Guest on Tom Cagley’s SPaMCast 468

Tom Cagley interviewed me for his Software Process and Measurement Cast (podcast) a couple of weeks ago and the podcast is live. See SPaMCAST 468 – Johanna Rothman, Create Your Successful Agile Project. We had a blast. I ranted and raved (as I am wont to do) and had a great time discussing some of

MPD, writing

Writing Workshops Registration Open

I have finally finished recording the videos for my writing workshops. See Writing Non-Fiction Workshop 1: Enhance Your Business and Reputation (Q1 session starts Jan 2018) Writing Non-Fiction Workshop 2: Secrets of Successful Non-Fiction Writers (Q1 Session starts Jan 2018) The first workshop is about building a habit of writing. If you want to help people see

MPD, project management

What’s Your Project Problem?

Projects have problems. That’s why we select life cycles, approaches, and apply risk management as we proceed so we can manage these problems. What’s your #1 project problem? The nice folks at Mavenlink identified 5 major challenges in project management. Here are the top 3: Project plans and scheduling are not aligned (45%) Contention for

agile, MPD

Select Your Agile Approach Article Posted

Do you struggle with your agile approach? Sometimes, iterations don’t work for teams. Sometimes, flow doesn’t work. Sometimes, you need both. To celebrate the release of Create Your Successful Agile Project: Collaborate, Measure, Estimate, Deliver, I am writing a series of articles on Infoq. The first article, Customize Your Agile Approach: Select Your Agile Approach That Fits

agile, MPD

How Little Can You Do (& Still be Effective)

Back in Manage It!, I suggested that for requirements, the questions should be, “How little can we do?” and still have a great product. My argument was this: the longer the project (regardless of approach), the more risk there is. Can you reduce risk by reducing the requirements? That would allow you to release earlier

agile, MPD

Agile Practice Guide Interview with Mike Griffiths

Last year, I was part of a geographically distributed team who wrote the Agile Practice Guide. Shane Hastie interviewed us during Agile 2017. His interview (which was a ton of fun!) is here: Johanna Rothman and Mike Griffiths on the Agile Alliance/PMI Agile Practice Guide. I learned a ton from that writing experience: Geographically distributed agile

Scroll to Top