Keys to a Successful Software Development Project
by kvangork
- 1,747 views
Video at vimeo.com/kvangork...
Video at vimeo.com/kvangork
Presentation given at the 2010 Washington GIS Conference in Tacoma, WA.
Abstract: Software projects have a notoriously low rate of success. This presentation will convey keys to a successful project, gleaned from years of experience both as an in-house developer and consultant. We'll avoid buzzwords and fads, focusing on practical steps you can take to ensure a successful project.
Planning — You can't get anywhere without a map.
Infrastructure — basic tools to keep everything on course whether you're working solo on geoprocessing scripts or with 100 people on an enterprise integration.
Communication — Listen to the right people and develop a decoder ring to understand what they mean.
I got some push back afterwards regarding my comments on estimation, so I'll clarify my thoughts:
Accurate estimation (+-25%) is impossible on any project big enough to be interesting. The reasons for this are two: nothing is as simple as it looks, and good software development is responsive to an evolving understanding of the need.
One exception to my estimation impossibility theory is if you're building something you've already built in the past. If that's what you do...you have my pity and you're probably not even reading this.
Accessibility
Categories
Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Likes
- 4
- Downloads
- 0
- Comments
- 1
- Embed Views
- Views on SlideShare
- 1,729
- Total Views
- 1,747
1–1 of 1 previous next
Need to know the big picture/end goal.
How do the parts fit together?
People don’t read
Things change
easy to re-prioritize.
Avoid Illusion of Agreement
Think of specific users, real or imagined.
Solo Options: Excel, Notebook
Teams: Post-it Notes or...
Solo Options: Excel, Notebook
Teams: Post-it Notes or...
Solo Options: Excel, Notebook
Teams: Post-it Notes or...
Solo Options: Excel, Notebook
Teams: Post-it Notes or...
Once this section is over, you can get up and leave, or take a nap.
This is the one true KEY.
Just call it SVN to get through your IT department.
A team can’t work together (or stick to the plan) unless they meet frequently to get synchronized. Do the same thing.
At least twice a week.
Basic questions - What did you work on? What are you working on? What are your problems?
Watch for people checked out, like number 75 here.
A productive developer is a happy developer. An enthusiastic manager is an involved manager.
Otherwise you’ve got trouble starting.
Don’t keep people in the dark.
Cultivate trust. How? BE TRUSTWORTHY.
Beta testers.