http://bolour.com/blog Wed, 20 Aug 2008 16:41:56 +0000 http://backend.userland.com/rss092 en Iterative time-boxing, or ITB for short, is the strategy of strictly time-boxing successive stages of work on a software requirement. In this note, I'll contrast ITB as a planning technique with conventional estimation planning for iterative and incremental development (IID), and consider its effective use. Agile IID typically works like this: ... http://bolour.com/blog/2008/08/iterative-time-boxing/ Here is an excerpt from the introduction to my recent write-up on monads. Monads in functional programming provide a framework for aspect-aware computations to be composed to build higher-level aspect-aware computations. An aspect-aware computation is some basic computation that has been enhanced, augmented, or, more generally, just transformed, to become aware ... http://bolour.com/blog/2007/02/monads-through-pictures/ There's been a lot of interest recently in the application of lean principles to software development. See for example the 2003 book Lean Software Development: An Agile Toolkit for Software Development Managers by Mary and Tom Poppendieck. A basic principle of lean thinking is pull. In pull, the materials ... http://bolour.com/blog/2006/10/some-consequences-of-pull/ The GANTT chart, as embodied in Microsoft Project, has become the de facto method of representing software development plans in many organizations. This is unfortunate. For, the precise temporal positioning of all tasks within a timeline is seldom necessary for managing the progress of a software project. GANTT charts reinforce two ... http://bolour.com/blog/2006/10/task-dependencies-in-plans/ The benefits of collective code ownership are well-known. Everyone in the team needs to be able to contribute to every part of the code base. But collective code ownership has an Achilles heel. The quality of the code can degrade as team members try to evolve unfamiliar parts of ... http://bolour.com/blog/2006/10/code-stewardship/ Iterative and incremental development (IID) is the established practice for dividing software projects in time. IID is often interpreted to mean a succession of complete development cycles, meaning that each iteration includes within its temporal boundaries the analysis, design, implementation, and deployment of the features produced in that iteration. But ... http://bolour.com/blog/2006/10/iteration-pipelining/ Specialization in teams allows team members to do what they are good at and what they like to do. There are at least three types of specialization in software development teams: functional specialization, subsystem specialization, and technology specialization. Here I'd like to focus on functional specialization. A role is a ... http://bolour.com/blog/2006/10/a-view-of-development-roles/ Team culture and software architecture have this in common: once the basic patterns have been established in each, it is relatively hard to change them, even though, at the same time, incremental change is a necessary part of their growth. To set the stage, here are some examples of hard-to-change team ... http://bolour.com/blog/2006/10/culturetecture/