I spoke about hiring for cultural fit at Communitech in Waterloo, CA earlier this year. While I was there, I met another author, Yvonne Chypchar. (She wrote a terrific book about knowing your value, Be the Smart Girl: Money and Your Value: Navigating the world of part-time and summer jobs for girls 12 to 17.) Yvonne […]
Do you have a title such as product manager, product owner, or business analyst? We hear these titles all the time. What does each do? Here is how I have seen successful agile projects and programs use people in these positions. Note that I am discussing agile projects and programs. The product manager creates the
As I work with more clients on their programs, I see that what might work for a product owner for a team does not work for a program. In a program, if the product owner is shortsighted, does not take advantage of agile/lean for updates, and does not have small features, the program loses momentum.
Agile product leaders (product managers, product owners, and business analysts) all have one goal: How do I support the team in their quest to deliver better and faster? Product leaders do this by helping the team plan with minimums, and continually replan. These two workshops help you do that. I offer two versions: for teams,
I published my most recent newsletter, Creating Trustworthy Estimates, this past week. I also noted on Twitter that one person said his estimates created trust in his organization. (He was responding to a #noestimate post that I had retweeted.) Sometimes, estimates do create trust. They provide a comfortable feeling to many people that you have
Creating Trustworthy Estimates Do the people who ask you for estimates trust your estimates? It’s difficult to build trustworthy estimates. Here are three tips you can try for estimates that work for you, not against you. Tip #1: Never provide a single-point estimate. When people ask me for an estimate, I provide a percentage confidence
I’m happy to announce that Predicting the Unpredictable: Pragmatic Approaches to Estimating Cost or Schedule is done and available. It’s available in electronic and print formats. If you need a little help explaining your estimates or how to use estimation (even #noestimate), read this book.
Several years ago, I had a senior VP as a client. He wanted his managers to work as more of a team. He thought they were not working together for the good of the company. I asked him why he thought that. “When they estimate, they don’t work together on an estimate. They each estimate
There’s a twitter discussion of what people “should” do in certain situations. One of the participants believes that people “should” want to learn on their own time and work more than 40 hours per week. I believe in learning. I don’t believe in expecting people to work more than 40 hours/week. My experience is that
As more of my clients transition to agile, many of them have a fascinating question: How do I assess who is doing what on my team? When I ask why they want to know, they say it’s all related to reviews, rewards, and general compensation. They are still discussing individual compensation, not team compensation. When