Hopefully, it’s obvious to all and sundry that this blog has been transformed. As you can see, I’m in the middle of launching a new business site: Agile Pain Relief Consulting. The blog will always be called “Notes From A Tool User,” and notesfromatooluser.com will always work, but from now on it will be a 301 redirect to this site. The upshot—please do not adjust your set. It is functioning as intended.
The transformation is far from complete—some structural work and a lot of writing are left to do. Please excuse the mess. In the meantime, I’m going to get this blog back on track.
This week’s Quick Links:
We’re hearing a lot about Toyota’s woes in the news. Hal Macomber thinks the common claim that Toyota lost its focus in attempting to become the world’s largest car manufacturer is wrong—read: What Is Going on with Toyota and Toyota’s Lesson for Project Managers for more.
Dave Nicolete (riffing on some comments by Dave Rooney) suggests a simple way for estimating a team’s initial velocity for its first few iterations. This is the problem that teams new to Agile have. Management wants an initial estimate of how much work will get done before the product is released and the team doesn’t have enough experience to give it.
Sandy Walsh (a former colleague from Andyne Computing) is writing an interesting series on the importance of readable code: A Tale of Two Code Bases and Your Code is the Other Team Member .…
In Goal-Oriented Daily Stand-Ups, Joakim Karlsson offers the idea of setting a daily team goal, which helps to ensure that the individual tasks toward the team’s goals.
In the early ’80s, the department of Computing Science at Queen’s University got its first Vax 11/780. At the time, my father complained that professors no longer talked but just emailed each other even though their offices were only 10 feet apart. Phil Jeffs notices the problem continues: Don’t email me. I’m sat right next to you.