I am doing a google hangout with Marcus Blankenship on April 10. We’ll be talking about estimation and my new book, Predicting the Unpredictable: Pragmatic Approaches to Estimating Cost or Schedule. The book is about ways you can estimate and explain your estimates to the people who want to know. It also has a number […]
Some of my coaching clients have way more to do than they can manage. Some of my project portfolio clients are struggling with how to say no. My most recent Pragmatic Manager newsletter is all about what to do when you have too much to do. Read it at Do You Have Too Much to
In many of my transitioning to agile clients, the managers want to know when the project will be done. Or, they want to know how much the project will cost. (I have a new book about this, Predicting the Unpredictable: Pragmatic Approaches to Estimating Cost or Schedule.) Managers ask for estimates because they want to
Every time I work with a client or teach a workshop, people want more ways to visualize their project portfolios. Here are some ideas: Here is a kanban view of the project portfolio with a backlog: And a kanban view of the project portfolio with an “Unstaffed Work”
I’ve been talking with clients recently about their managers’ and HR’s transition to agile. I hear this common question: “How do we manage performance of the people on our agile teams?” Reframe “manage performance” to “career development.” People on agile teams don’t need a manager to manage their performance. If they are retrospecting at reasonable
Update: I titled it Predicting the Unpredictable. I have finished the content for Essays on Estimation. But, I need a new title. The book is more than loosely coupled essays. It reads like a real book, with progression and everything. I have a number of ideas. They are (in no particular order): Predicting the Unpredictable:
I have an article up on agileconnection.com called Common Misconceptions about Agile: There Is Only One Approach. If you read my Design Your Agile Project series, you know I am a fan of determining what approach works when for your organization or project. Please leave comments over there. Thanks! Two notes: If you would like to
For years, we bought the cone of uncertainty for estimation—that is, our estimates were just as likely to be over as under. Laurent Bossavit, in The Leprechauns of Software Engineering, shows us how that assumption is wrong. (It was an assumption that some people, including me, assumed was real.) This is a Gaussian (normal) distribution.
Many organizations create teams by their architectural part: front end, back end, middleware. That may have worked back in the waterfall days. It doesn’t work well when you want to implement by feature. (For better images, see Managing the Stream of Features in an Agile Program.) Pierce Wetter wrote this great article on LinkedIn, There is
Is there room for functional managers, such as development and test managers, in agile organizations? Maybe. It depends on whether they take the role of an agile manager. If you have organized as a feature teams-based organization, the functional managers (development, test, analysis, whatever) can take these responsibilities: Develop trusting relationships with the people on