1 / 18

Thoughts from a Small Team Software Engineer

Thoughts from a Small Team Software Engineer. Things you need to know but won’t try to understand until you need them. Don Gilman, P.E., MCP. SP/MP/Pro. Presentation. People Process Tools. People. Does the customer have a clue?

erica-summers
Download Presentation

Thoughts from a Small Team Software Engineer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Thoughts from a Small Team Software Engineer Things you need to know but won’t try to understand until you need them.

  2. Don Gilman, P.E., MCP SP/MP/Pro

  3. Presentation • People • Process • Tools

  4. People • Does the customer have a clue? • Who fills the QA, Deployment, Documentation, Artist, SysAdmins roles? • Mythical Man Month • Leads • Assistants • Do you want survivors?

  5. The True Balance

  6. People Details • Interviews • Getting Up to speed • Templates • Guides • Success breeds success • Keeping on track • Their first Lead • When they run off the road • When you shoot them

  7. Process • Are you in the right race? • How do you win? • Who decides if you win? • What are the risks? • Does your sponsor have skin in the game? • What is really due when? • Has this race been run before? • Is the finish line moving? • Does this race really matter in your career or life or the world?

  8. Process – more tactical • PAD Review (see Props) • High level design/partitioning • Code Reviews/Unit Testing • General SQA • Documentation Patterns • Configuration Management • Deployment/Testing

  9. Props (Templates/Databases) • Vision & Scope • Project Artifact Document (PAD) • Estimation via Use Cases • Requirements Listings • Risk Listings • Scrum, not for breakfast anymore

  10. Props – Building and Deploying • Defects/Change Orders • QA/Build/Server Stat Notices • Debuggers • Code Blocks • Change Management Tools • Development, Test, and Production Servers • Guides

  11. Groupware/Email

  12. Forums

  13. Mantis

  14. What I’m Reading • Software Development Magazine (www.sdmagazine.com) • CrossTalk (www.stsc.hill.af.mil/crosstalk) • MSDN Magazine • Better Software(www.stickyminds.com) • The Rational Edge (www.rational.com) • www.software-engineer.org • www.seir.sei.cmu.edu

  15. SE Books I’ve read that matter • How to Win Friends and Influence People, Carnegie • The E-Myth Revisited, Gerber • Planning Extreme Programming, Beck/Fowler • Mythical Man Month, Brooks • Agile Project Management w ScrumSchwaber • MS Solutions Framework Papers • Software Requirements, Wiegers • Decline and Fall of the American Programmer, Yourdan • Productivity Management, Keene Inc.

  16. Things I’m Still Working on • Focus • Shooting people • Follow through • Technical vs Administrative Path • Keeping current • Finding the best tools

  17. What’s In it for Me? • I’m always hiring in both locations • Educational Opportunities • Interns for 485/685 • Masters Thesis • Resume/Publication Opportunity • Compensation • Named Credit/Software/Goodies • Hourly • GAR • Royalty Compensation

  18. Where to find me dgilman@tamu.edu dgilman@advancedgaming.biz http://esl-seg.tamu.edu http://www.computerharpoon.com http://esl.tamu.edu http://ecalc.tamu.edu

More Related