Trust-Driven Development Contents
This book has four sections:
Starting a new project
We’ll cover two important parts of starting a new project.
- What information do I need to start? And just as importantly, what information don’t I need?
- It’s entirely possible to make decisions on day one of a project that cause problems that are hard to solve. We’ll want to avoid those.
Day to Day
We’ll talk about the heartbeat of a project at two scales. The first is daily. Issues about a project on a day-to-day basis include:
- What does an effective and non-boring standup look like?
- How do you choose what to do next?
- What makes pair programming sustainable?
- Effective testing for the whole project?
- Why continuous integration and deployment is super-helpful
Week to Week
We’ll also talk about the heartbeat of a project at the iteration scale, usually one or two weeks.
- Why split a project into iterations?
- What makes for an effective iteration planning meeting, or whatever you want to call the thing where you plan the next two weeks?
- How to do the least amount of estimation and still get value.
- Retrospectives. You should have them.
One way or another, we all face crunch time
- Managing deadlines
- What do do when something goes wrong?
- Identifying problems before they get out of hand.
- How to improve a hostile environment
- Switching a project from active to maintenance
Looks Interesting, Buy It!