Development projects 101

Introduction

Projects are all about delivering software to the users. But how can you assure the right quality? How can you involve the correct people? How can you deliver on time or cost? Why are these challenges so hard?
Here's a short reminder or summary of some practises I've had success with.

Build a small team of super people

You need a small team to start the process. They do not need to be involved full time, but they should be dedicated to the project, so that anything related to the project should have full attention when needed.
Project leader, super user, developer, designer, tester. You should all be involved and ready.

1. Get to know the problem domain!

Involve the users and make friends. This makes sure you deliver the right thing (and not just deliver things right). Get examples and experience real practise.

2. Ship as fast as possible 

Automate the deployment pipeline. Ship as little as possible to minimize risk. A calculator that only returns 0 is still a calculator. Not particularly useful, but it's still something that works and can be tested/viewed.

3. Test and iterate

At any iteration you should be able to go to production dependent on the deadlines.

1. Get the core functionality up and running
1. What constraints are there?
2. How to solve the problem as easy as possible?
2. Get user feedback
1. Does the basic functionality solve the problem?
3. Get experience 
1. Can the flow be better?
4. Iterate and refine usability

This enables a good feedback loop. And you make sure to deliver on time.

4. Make sure you plan for flexibility

Say no. Can it be differed? Always prioritize the most important things. Usually some minor changes can be done later, and the user can live with a workaround until then.

5. Involve all stakeholders

System development is also about changing people and the organization. User training and involvment from the business side are important.

Some general considerations

In Rework they talk about four letter words: need, must, can't, easy, just, only, fast. Who hasn't heard those words in a project. The problem, as the authors also say, these words introduce a black/white situation. Implying that the work being done is a minor thing. This is a fall trap and I will say it's in the category "assumption is the mother of all fuckups".

Summary

It's a hard practice, but a good team and dedicated people makes good quality solutions.
So don't have FEAR (False Evidence Appearing Real), www.agilemanifesto.org.