Big news! I’m thrilled to announce that Hiring the Best Knowledge Workers, Techies & Nerds: The Secrets and Science of Hiring Technical People is available in PDF from Dorset House. For those of you who sent me private email, I will try to email you to let you know over the next week.
I’ve been working on agile program management and a colleague emailed me about his program. He’s having trouble seeing how to do agile on a large program. The customer wants to see a working system before they add the features, so the customer thinks the program need to provide “all” the architecture, with some hard-coded
Some teams don’t do demos at the end of their iterations. Many of the teams who don’t do demos also have trouble finishing all the stories they committed to at the beginning of the iteration. They continue, iteration to iteration, not always finishing, not getting to releaseable at the end of the iteration. And, sometimes,
Who’s in Charge of Quality? At the Agile 2010 conference a couple of weeks ago, I heard many people say, “When QA gets the software, …” In an agile project, that makes no sense to me, unless the team has not developed its own definition of done. In more traditional projects, the people in the
I have been delinquent for those of you who subscribe to my email newsletter. I have not published one since April. On the other hand, I just posted Park Projects You Can’t Staff, For Now. The next newsletter is scheduled for Thursday morning. In case you’re wondering, I post the most immediate past newsletter when
So I’ve spoken about women and other kinds of traditional diversity, personality and experience, new grads, and now it’s time to discuss a difficult topic. What about “overqualified” people? People who have tons of experience are looking for jobs. Too often, hiring managers don’t want to hire them because the manager thinks the candidate will
Last week at Agile 2010, Joshua Kerievsky and I facilitated an Open Jam session (open space) about what done means. We discussed a variety of points. I believe we eventually agreed that context matters. It’s important to know what your product success criteria are. If you don’t use a project charter where you define success
Josh Kerievsky has an intriguing post about . The idea is that a story is not done until: A story isn’t done until it is being used by real users in production and has been validated to be a useful part of a product. I have trouble with this definition: The development team is dependent
I have a column up on Stickyminds, Six Behaviors to Consider for an Agile Team. Please do leave comments there.
I hear this story again and again. A hiring manager can’t find the right candidate. Why? You would think it would be easier to find great candidates, because so many people are out of work or are looking for better jobs. But that’s exactly why it’s so hard for hiring managers to find people–there are