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

Thoughts from a Small Team Software Engineer

Embed Size (px)

DESCRIPTION

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? - PowerPoint PPT Presentation

Citation preview

Page 1: 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.

Page 2: Thoughts from a Small Team Software Engineer

Don Gilman, P.E., MCP

SP/MP/Pro

SP/MP/Pro

Page 3: Thoughts from a Small Team Software Engineer

Presentation

People Process Tools

Page 4: Thoughts from a Small Team Software Engineer

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?

Page 5: Thoughts from a Small Team Software Engineer

The True Balance

Page 6: Thoughts from a Small Team Software Engineer

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

Page 7: Thoughts from a Small Team Software Engineer

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?

Page 8: Thoughts from a Small Team Software Engineer

Process – more tactical

PAD Review (see Props) High level design/partitioning Code Reviews/Unit Testing General SQA Documentation Patterns Configuration Management Deployment/Testing

Page 9: Thoughts from a Small Team Software Engineer

Props (Templates/Databases)

Vision & Scope Project Artifact Document (PAD) Estimation via Use Cases Requirements Listings Risk Listings Scrum, not for breakfast anymore

Page 10: Thoughts from a Small Team Software Engineer

Props – Building and Deploying

Defects/Change Orders QA/Build/Server Stat Notices Debuggers Code Blocks Change Management Tools Development, Test, and Production

Servers Guides

Page 11: Thoughts from a Small Team Software Engineer

Groupware/Email

Page 12: Thoughts from a Small Team Software Engineer

Forums

Page 13: Thoughts from a Small Team Software Engineer

Mantis

Page 14: Thoughts from a Small Team Software Engineer

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

Page 15: Thoughts from a Small Team Software Engineer

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 Scrum Schwaber

MS Solutions Framework Papers Software Requirements, Wiegers Decline and Fall of the American Programmer,

Yourdan Productivity Management, Keene Inc.

Page 16: Thoughts from a Small Team Software Engineer

Things I’m Still Working on

Focus Shooting people Follow through Technical vs Administrative Path Keeping current Finding the best tools

Page 17: Thoughts from a Small Team Software Engineer

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

Page 18: Thoughts from a Small Team Software Engineer

Where to find me

[email protected]@advancedgaming.biz

http://esl-seg.tamu.eduhttp://www.computerharpoon.com

http://esl.tamu.eduhttp://ecalc.tamu.edu