One of the most often used terms you hear in a meeting at Microsoft is “that's the dumbest thing I have ever heard“. Sometimes this is true (remember Hailstorm?), sometimes its not (combine Excel and Word into one suite of well-integrated products). I've been kicking around ideas for starter kits for Whidbey. A starter kit is an out-of-the box pre-built app that should solve a specific customer problem (check the existing ASP.NET starter kits). I asked two colleagues for their opinions on my idea. One said “That's the dumbest thing I have ever heard“ (PS: you rock Joe), the other said “that's a great idea, I spent the last summer doing this!” (PPS: you rock too Shreyas).
Your mission: Decide who's right :)
The idea is to create an intranet web site starter kit for a corporate IT department, including features like asset tracking, a help desk ticket system, reporting, FAQs, employee phone book, dynamic Org Chart, downloads, etc. A customer could get the starter kit, change some settings and be up and running in minutes (rather then months).
Why create this starter kit? Because our developer division doesn't focus much attention on IT apps (try and find good examples on using Active Directory) and I think we could create a compelling application that you could drop into your company and get working easily.
PS - If you do like this idea, prioritize/stack rank the features you think are most important. Each feature has a letter next to it, so if you think something is a must have, add it as a PRI 1 in your response.
MyHelpDesk Starter Kit Details
So what do you think? Also, is making Active Directory and Windows authentication a requirement okay? Does the app need to play with Windows Sharepoint Services and Sharepoint Portal Server?