Me: I live in Silicon Valley with my wife, child and cat. I have worked at Microsoft since I graduated from College, both in the Macintosh Business Unit on products such as Outlook Express, Entourage, IE, and Virtual PC and in Windows Live on Hotmail, Calendar and People. I am currently a Principal Lead Program Manager on the Windows Live Social Networking team. I basically manage a team of Program Managers responsible for delivering features to support our web and client applications. I've been blogging since 2001 and like to play around with .NET in my spare time working on projects such as dasBlog (the blog that powers this site) and Send to SmugMug (an application for uploading photos to SmugMug). I blog about a number of technology and productivity related topics.
Powered by: newtelligence dasBlog 2.3.9074.18820
Disclaimer The posts on this weblog are provided "AS IS" with no warranties, and confer no rights. The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
© Copyright 2010, Omar Shahine
E-mail
And not the physical kind of Waterfall, the kind that is predominantly used for software development.
The Microsoft Product Lifecycle (last time I checked) was basically Waterfall, where you plan -> spec -> dev -> test. This is how Office is developed (Windows and Mac) and has worked well for at least a decade. However, we’ve found that Waterfall is no good for developing services and fast iteration of your product. That’s where interest in Agile development methods like Scrum have come into play.
As I’ve mentioned before, we kicked Waterfall to the curb last year and haven’t looked back. Waterfall 2006 looks like a great fake conference . Some of the papers/links are hilarious (well if you develop software for a living).