by Robert D
The journal linked below talks about development strategies for web sites. They term the default non-strategy “ad-hoc” development, which is characterized by a person-to-person development process where plans are made up on the spot between customer and developer. This method is messy, and a lot of problems can arise from thinking in the short term. There’s also SDLC and rapid prototyping, which we went over in class. These methods are less costly and messy than the ad-hoc strategy.
The journal then goes on to point out the seven ways we make the process longer and more unwieldy than need be. These are: overproduction (focusing on developing things when there’s already enough in place), transportation (the issues involved with having several people work on the project with specialized skills; for every hand-off, you need to bring someone up to speed), inventory (keeping information on what’s going to be and what won’t be), extra processing steps (when red tape goes wrong), waiting (which you see a lot with the ad-hoc strategy), motion (everything you waste physically during development, but not on hardware and so forth), and defects (fixing problems and how you handle them).
It’s important to keep the right-sized team for your job. Don’t use a massive and highly-specialized team for a routine job. There’s wasted time and energy in that type of situation. The journal instead outlines the benefits of lean development: using just what you need. Smaller teams that know what they need to do will function far more effectively than large teams that need to communicate and brainstorm and so forth.
Ellen, B. “Lean/Agile Methods for Site Development” 2005 Oct. http://0-search.proquest.com.opac.library.csupomona.edu/abicomplete/docview/199927274/135239656DC58AEAE0B/3?accountid=10357