Tim is a long-time programmer (since 1979), contributing editor, reviewer, author. He has been active in Design Patterns, Object-Oriented Design, and Agile software development.
He is a consultant, programmer, tester, teacher, agile team coach, manager, and writer.
Tim is one of the crew of experts at Industrial Logic, a premier agile consultancy, eLearning vendor, and thought leader. Here he joins with Bill Wake, Joshua Kerievsky, Woody Zuill, Arlo Belshee, Mike Hill, and other industry experts to help people develop the skills that will make them awesome.
In addition to his contributions in "Clean Code" and "Agile In A Flash", Tim's articles appeared in the C++ Journal, Pragmatic Bookshelf, InfoQ, CIO, and SmartBear.
Tim muses about of his experiences and ideas on the Agile Otter blog and the Industrial Logic company blog.
Your modern “agile” transition has been a bit of a nightmare. On top of all the work you normally do, you have extra meetings, extra practices, extra responsibilities, more pressure, less accomplishment, and no time to think whatsoever. Not feeling “empowered?” Is this what the first Scrum and XP teams did? And yet, there are people in the world who seem to be legitimately enjoying their experience. They are doing the same things you are doing: they have morning meetings, sprints, story-points (those who still estimate at all). Why do they like this? If “agile” methods are such well-defined processes, why don’t all the people who use them have the same experience? Tim and Ruud suggest you’ve been given a weak or dead strain of agile -- more like inoculation than enrichment. You don’t have to settle. If your company wants you to have an Agile team, get the real thing. Learn how to unencumber your team, empower people, and reach a higher level of development. Take agile back for yourself and your team.
More, faster: everybody wants that.
Low productivity makes products late and expensive, frustrating both teams and customers.
But what is productivity? Why is it so hard to measure?
Organizations want higher productivity, but use industrial-age models better-suited to assembling widgets than developing software.
We’ll explore a model that works for software teams.
Learn several ways to boost - or drag down - productivity in your projects.
You’ll walk out with concrete techniques to apply in your context.