Hello, I need help deciding which is the best software development process for the project I'm involved in. I'll outline the project features.

The project consists in building an application for a device that reads payment cards and performs online payments.
The requirements are almost completely set (I have a 300 pp specification) and very stable. Only minor changes are expected.
The team is composed by... hmmm, let me think... ME! Only me. My boss is supposed to help me, but only from time to time.
It is a small project. I think that it should take me less than a year to finish it if I don't find major problems.
The language of choice is Java.

My company develops software without doing any analysis, design, etc. However, I wanted to do things the right way and follow a suitable process. But I want a lightweight process, since my project doesn't demand a full-fledged classic process. That's why I got interested in agile methods. But after browsing some XP sites, I found out that XP is intended for risky projects with unstable requirements, which is not my case.

So, can somebody advice me on the best process to follow? Should I try another agile process instead of XP? Or is XP fine for me anyway? Or should I forget about agile processes and try something different?

Thanks in advance

Hello.

Probably my response is too late, but anyway.

It doesn't metter how you will call your process - eXP, SCRUM, etc. THe thing is that process should HELP you to make your project. Process for Process is not the goal - I have blog, there is some information concerning SCRUM - http://litoshenko.blogspot.com .

If you have 1-year project for 1 person - you could still use SCRUM for example. It would be much easier for you to implement this Project if you will split your Scope into 2-4 week phases - Iterations. EAch iteration you will set Goal - implement features A and B to add for the Project ability to make that that and that... - it is much easier for the people to work with short-terms goals. Each iteration you and your boss will see result of your work, it is quite good in terms of motivation. YOu will see which part f work is done, what should be done till the end of the Year, you will be able to estimate if you are on Track, or you need change something in your development Processes.

Also, it is quite good to use some practice from eXP, like Unit Testing - it will help you to make your code maintainable, it will have less Bugs. It is quite good to use TDD (Test Driven Development) - it will help you to avoid reworking of the methods, so you will spend less time for development.

Let's say that your productivity is X functional points per day. Smart processes will help you to make it 2X functional points per day - not because you will type faster, but becase you will not waste your time on unnecesary things and will concentrate yourselfe only on things which are important for the Project.

I will recomend you "Deadline" - DeMarco - it si not about Agile, it about suitable Processes, about life of Projects. Here is a _link_ to this book - http://www.amazon.com/Deadline-Novel-About-Project-Management/dp/0932633390

Best Regards,
Vladimir

I can understand soem of hte points being raised here, but I'm sorry I don't agree.

B&B in Stratford-Upon-Avon