Monday, February 17, 2003

This sort of approach towards consumer-oriented software has a lot of promise. I've talked about the need for new software designers who don't know how to write software. That was about 4 months ago. Turns out, MSFT was doing this very thing for a few years now. Humbling...   -----Original Message----- Posted At: Monday, February 17, 2003 2:01 PM Posted To: sellsbrothers.com: Windows Developer News Subject: Microsoft Gets a Clue From Its Kiddie Corps http://www.sellsbrothers.com/news/showTopic.aspx?ixTopic=447 A bunch of kids gather in a real-world like setting to design an app, only consulting an actual software engineer after the spec is done. Not only does the core app sound cool, i.e. groups of contacts that play/chat together in an online environment, but the way they designed it sounds cool, too. I'd like to grab a set of my customer base and hang in a trendy Seattle downtown warehouse for a month, too, but my customers are all too old to get away for that long. : ) Posted by Chris Sells on Mon, February 17, 2003 @ 1:06PM      MP methodology (as in Microsoft Programming) Scott Gutherie writes about a typical MSFT dev cycle. Notice how the automated tests done after the features are completed. XP on the other hand calls for tests to be written before the features are done. The MSFT way will get the features faster, thus unblocking the QA to work on automated tests. This makes sense when you have about 1-to-1 ratio between developers and testers, but if the team isn't structured in this way it may make sense to slide the dial more toward XP way. How does your team makes it?

Site Statistics

© Copyright 2003 Alexis Smirnov. Last update: 5/6/2003; 5:43:05 PM.