What should managers expect from their agile teams? Should they expect perfect code, or on-time delivery, or cheaper projects? Too many people sell agile as a way to get better, faster, cheaper. The problem is that you can get better code, faster projects, and cheaper results as an outcome of agile across the organization. We […]
See Your Agile Collaboration Traps In honor of the impending Create Your Successful Agile Project book release, I decided to send you a four-part series about agile traps. Yes, one for each piece of the subtitle. This one is the collaboration trap. Here are three common collaboration traps: Your team is a component team. (The
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
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
You may think the #MeToo tag doesn’t have anything to do with product development. Not so fast. When people behave badly (more often it’s men than women, but it can be either), the people suffer. When the people suffer, the product suffers. It suffers in development and it suffers in release. The issue is this:
Jen Bunk interviewed me for the People Stack Podcast #32. We had a wide range of topics: How I started as a consultant The advancement (or lack thereof) of women in tech. Understanding what the problems are. (Yes, the problems are always a people problem. I managed to bring in the idea of the project
Henny Portman just published a review of Manage Your Project Portfolio. See his review at Review: Manage your project portfolio. He included a terrific image (go to the review to see it) about how you can think about the entire process, from soup to nuts. Here is an excerpt from his conclusion: “… a must
Yegor Bugayenko asked me to be a guest on his podcast to talk about Hiring Geeks That Fit. I gladly accepted and the podcast is now up: Shift-M/10. We spoke about many issues in hiring: Laundry list/shopping list problem in job descriptions Starting with a “test” or a phone screen (I need to write a post
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
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