Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working on a company's project alone at the moment, but the company is getting soon a junior developer whom I will be mentoring. Considering he will be learning a lot in first few days I am planning on using pair programming for first couple of weeks. I believe that doing pair programming would make daily standup a redundant practice. I definitely will keep the retrospective as well as tdd.

I wanted to ask if you would suggest any other agile practices that would benefit our small team of two developers? What have worked for you?

share|improve this question
Thanks @YannisRizos. I tried searching to no avail. Guess I'll have to try harder next time .) – Eimantas May 4 '12 at 7:15
Well I couldn't find an exact duplicate (wasn't really looking for one), but if the three questions I found answer parts of your question, please edit those parts out, we don't want folks spending time answering what you've already found an answer for. – Yannis May 4 '12 at 7:17
Daily standups are to rectify that communication suffers quickly as teams grow. If you work closely together all the time, you cannot improve on your communication and standups are not necessary. – user1249 May 4 '12 at 12:26
up vote 3 down vote accepted

I am doing it with a team of one currently (I have been promised help in the near future).

But I find it useful for planning (I drag in other developers to help in estimation processes so it is not just me) and tracking progress (for both me and the management team).

Also when other team members join they will be able to see what tasks are currently available to work on and be able to jump in and help.

During planning it still works for prioritization and the demo are still cool.

share|improve this answer
+1 agile is a philosophy, not a head count – Steven A. Lowe May 5 '12 at 3:09

You're assuming that daily stand-up is just for the developers. While it does have some benefit for them, it also has benefit for BAs, QA, etc. in having a regular time that they can hear what's going on and discover issues of miscommunication (most of the problems in software development), or which jobs are taking longer than initially predicted (allowing for minor reprioritisation, within the sprint, and for QA to know when they expect jobs to be delivered).

I have also worked on a team of two who used Agile estimation techniques and who kept a task board up to date, which is both useful and satisfying for the developers themselves and a very visible, constant representation of a sprint to the other stakeholders.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.