Comments
Big Government Software Projects: 11 Lessons Learned
Newest First  |  Oldest First  |  Threaded View
pavance
50%
50%
pavance,
User Rank: Apprentice
11/24/2013 | 5:08:51 PM
Re: Hard Earned Insight
yump. Gather requirements and go underground until done. While it smacks of waterfall, it's necessary to freeze, at some point, and, if you got it right, let the developers deliver. I used this time manage development and to go around and convince various stake holders that what we were doing was their idea ("Gee, I'm so sorry I argued with you, you were right." They had forgotten everything but the argument, because it was all ego.). Using agile builds trust and is a good way to gather requirements, but on a really complex project, you have to freeze and deliver. Managing expectations is what it is all about during that phase.
WKash
50%
50%
WKash,
User Rank: Author
11/19/2013 | 7:02:55 PM
Valuable points
There are some truly valuable lessons here, but especially your point about establishing one ultimate business owner, so stakeholders can't undermine the project; and your point about letting the business dictate the priorities and developers explain the consquences.  This is the ultimate frustration for many end users is a system designed by developers instead of designed for the business users. Thanks for sharing these.
LeonardD475
50%
50%
LeonardD475,
User Rank: Apprentice
11/19/2013 | 3:21:20 PM
Re: Public v. Private
Thanks for the thoughtful question.  I'd love to learn from others whether such outreach would fly in publically traded companies.  That said, most academics live inside of a "publish or perish" paradigm which, despite the altrusitic nature of medical research, can lead to pretty competitive environment.  No surprise here - whether in business, govt, or academia it helps to be referred.  We asked "who else should we be talking to?" and "would you mind if we said you referred us?" It went a long way.
RobPreston
50%
50%
RobPreston,
User Rank: Author
11/19/2013 | 10:32:37 AM
Re: Hard Earned Insight
The point Chris raises is something we practiced with the relaunch of InformationWeek.com on this new platform:
We drew in many business-unit ideas and contributions early on in the project, but at some point the project manager (kudos to Joe Wyka) narrowed the process to a few select stakeholders. We still have lots more to do and tweak in version 2.0 of this project, but we didn't let a succession of proposed incremental improvements slow down the launch. 
Alison Diana
50%
50%
Alison Diana,
User Rank: Moderator
11/19/2013 | 10:08:04 AM
Public v. Private
I wonder what, if any, differences there would be on a list compiled by someone at a similar position in a public company. For example, calling people to learn about "what they'd have done differently" might be a lot more challenging if you work in the private sector, where competitors certainly won't want to share their valuable (and competitive) information! Although I'd guess you can find similar size companies in different industries to discuss implemenations...
ChrisMurphy
50%
50%
ChrisMurphy,
User Rank: Author
11/19/2013 | 9:33:01 AM
Hard Earned Insight
This is must-read advice for anyone who leads projects. What I found really valuable: The advice that at 1 stage of a project you need to draw in lots of business-unit ideas and contributions, but then later shut those same people out so the team can deliver. Subtle, powerful insight.


IT's Reputation: What the Data Says
IT's Reputation: What the Data Says
InformationWeek's IT Perception Survey seeks to quantify how IT thinks it's doing versus how the business really views IT's performance in delivering services - and, more important, powering innovation. Our results suggest IT leaders should worry less about whether they're getting enough resources and more about the relationships they have with business unit peers.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Must Reads Oct. 21, 2014
InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
A roundup of the top stories and trends on InformationWeek.com
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.