Level: Intermediate to Advanced
Architect / Trainer / Coach
Benjamin Day Consulting, Inc.
We’ve all been on projects that suck, right? The team is super late. You’re working 27 hours per day, 9 days a week and you don’t have a prayer of delivering even close to on-time or on-budget. Everyone knows (but no one dares mention) that the code is garbage. You can’t even get a stable demo build. Your boss is angry. The customer is beyond angry. You hate your life and it’s bad, kid. Real bad.
Ever stop to think about how the project got that way? I mean, no one ever starts a new project thinking yup, this one’s definitely going to eat it.
In this session, we’ll talk about 10 different things you can do to get your project started right. From thoughts on databases, to automated builds, to requirements management, to just what the heck “done” means. We’ll cover these and more so you can do things right the first time and avoid yet another disaster project.
You will learn:
- Start from best practices rather than adding them when things go wonky. (e.g. create an automated, continuous integration build before you do your first check-in)
- No shared development databases and no test data...EVER.