201Re: [scrumdevelopment] Splinter Department
- Feb 4, 2002I'd say so if the technology is so whacked, bleeding edge, or untested that someone needs to first evaluate it. Wireless used to fit into that category, and in some cases still does.
> From: "Jonas Bengtsson" <jonas.b@...>
> Date: 2002/02/04 Mon AM 09:35:23 CST
> To: <firstname.lastname@example.org>
> Subject: [scrumdevelopment] Splinter Department
> I've just read "Exploiting Chaos: Cashing in on the Realities of Software
> Development" by Dave Olson. In his book he proposes a "splinter department".
> This department is a place where very uncertain ideas can be tested, a
> nursery for new ideas. For instance, if a person gets a bright idea he can,
> with the management's approval, go to the splinter department for a couple
> of months and experimenting with the idea. If the experiments turn out good
> he might start a pilot project and so forth.
> The main reason for this department is that some ideas are too risky to
> explore inside a project and that some ideas are distractions from the main
> goal of a project.
> Is there a need for such a department in a Scrum "environment"?
> To Post a message, send it to: scrumdevelopment@...
> To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
- << Previous post in topic Next post in topic >>