We exceed expectations, do we need Agile? We are organized and documented.
Can it be a hindrance to our workflow? Forgot to mention there is a lot of legacy code, and tons of bug fixes, its pretty dynamic.
In particular, Agile is a statement that you value:
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to change over following a plan
I'd be willing to bet that a 2-person team that's moving fast, exceeding expectations and building necessary stuff well is already doing all of the above.
I suggest getting your boss to read that manifesto, then sit down as a team with him / her, and work through the principles. Discuss each one, and identify areas for improvement. If your boss is dead-set on a particular methodology, you might do well to highlight the first point above :)
The training I attended said the ideal team size for scrum is 4 - 7 team members. I would say follow whatever makes you feel comfortable, as long as you deliver some value to your end users it is all good.
Having said that at my current work I am using a trello board to manage all my stories and find it helpful even though it is just two of us at the moment. If you have any more questions feel free
I am going to shamelessly promote my startup, check out http://askmeanything.me/ , to ask questions to founding engineers.
If you already doing efficient work, you don't need someone to join your team and to justify his existence to inflict methodology over your already working workflow.
Methodologies makes sense to organize large teams with diverse backgrounds and experiences.
Small, efficient, and already professional teams usually neither need babysitting nor organizing methodologies to do it's work.
"Small, efficient, and already professional teams usually neither need babysitting nor organizing methodologies to do it's work."
... you're right, most likely because that team is already Agile.
Scrum - Cialas(TM) for a manager's CV[1].
1 - Don't take Scrum if you are responsible for delivering a product. To avoid long term WTF, seek another job if your stand ups last more than 4 hours. Scrum does not prevent the spread of defects. If you have any sudden decrease in productivity, stop taking Scrum and call your developers immediately.
Why tell your development team you are incorporating Scrum? Because, sooner or later, when the moment is right, you can spring it on them and get the keyword on your CV.
I would ask your boss this question.
Secondly, there are many Agile methodologies. The first step should be to sit down as a team and work through the manifesto, identifying areas for improvement.
Only once that's done is there any point in thinking about choosing a methodology.
The point was to encourage our fellow HN member to be open minded and try it for a short period of time. From there he can determine if the change has begun to yield any value or not.
Suggesting a team 'try a methodology for a week' is inviting a train-wreck.
Let's say the OP decides to adopt Extreme Programming.
How long would you say that a team with zero experience in that methodology would take to get to the point where they're practising it well enough to perform a useful evaluation of the consequences?