Wayne Allen's Weblog
pragmatic agility
-
Evolution of a Kanban board
In No More Iterations I showed our 1st attempt at a kanban board. Now that we have a little more experience I'd like to show you where we are now and where we stopped on the way.
-
Throughput vs. Velocity
Throughput and velocity are ways of measuring how fast a team can do work. Knowing how fast a team is going allows the team and their stakeholders to know when something is going to be done.
-
Corey Ladas explains Scrum-ban
Cory has a great post titled: Scrum-ban | Lean Software Engineering. In it he describes how a team can take advantage of kanban within a Scrum environment.
-
Another New Bike
Previously I posted about my new V-Strom which is a nice bike. However, after taking it on something more difficult than gravel roads and compared to my wife's Honda CRF150 I knew I needed something much lighter, more dirt oriented, but could still be ridden on the street.
-
The “Why To” Manual
Hank Wallace turned me on to a post by Allison Shapira where she summarizes a key point from Rob Walker's writeup of the Blue Man Group - the "Why To" manual.
-
Miško Hevery on Writing Testable Code
Miško Hevery has written a great summary of some basic coding rules for testability in his post Writing Testable Code.
-
New Bike!
My new bike is a 2005 Suzuki DL1000 otherwise known at the V-strom. I'm looking forward to getting to know it a lot better. The previous owner put a lot of aftermarket farkles on it including heated grips (incredibility useful as it was 40F on the way home) and a custom seat which seems great so far.
-
12 Learnings From My First Turn As Startup CEO
Jason Goldberg has a great post on some of the things he learned while CEO of Jobster.com.
-
Ten Reasons High-Tech Companies Fail
Planning on starting your own company? Here are some good points to consider from High Tech Strategies - Ten Reasons High-Tech Companies Fail
- Lack of Market Focus
- Excessive Pace of Product Improvement
- Incomplete Products
- Undifferentiated Products
- Channel Mismanagement
- Failure to Establish the Right Competitive Barriers
- Using Price Alone To Drive Market Transformation
- Improper Use of Advertising
- Misinterpretation of the Technology Adoption Lifecycle Model
- Irrelevant Market Research
-
Production vs. Attendance on Teams
Jeffrey Phillips wrote a nice post on Accountable for production not attendance. In it he argues that most knowledge workers should be treated like virtual workers – they should be held accountable for their production, not their attendance. The implication is that the results of the work is far more important than when or where they work. This is something I have given a great deal of thought to and agree with in principle. However, the focus here is on the individual. What if the individual works on a team?