Hi All, I've read a lot about Agile Methodologies for software development, SCRUM, XP, KanBan, AUP, and so on. All the methodologies include the definition of a team which can range from less than 10 members (scrum) to large teams (30+). But, what if you are developing a software where the only team member is you. What method to choose? ¿Scrum because there are few artifacts and roles and that let you be the Product Owner, Scrum Master and developer at the same time? ¿Do you need to follow strictly a methodology? or ¿is better A task list, a schedule and a lot of courage? ¿It's correct to think in play different roles for the same project?
I'll appreciate your comments.
Pinned topic What is the right development process for a one member "team" ???
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-08-18T13:16:16Z at 2010-08-18T13:16:16Z by Kruchten
BobPalank 120000PN206 Posts
Re: What is the right development process for a one member "team" ???2010-08-18T11:25:28ZThis is the accepted answer. This is the accepted answer.A well known and reliable author showed how RUP or OpenUP could be effectively tailored down for a team of one for a one week project. I'm on vacation, but others might post the author.
Kruchten 120000ETQP7 Posts
Re: What is the right development process for a one member "team" ???2010-08-18T13:16:16ZThis is the accepted answer. This is the accepted answer.
- BobPalank 120000PN20
University of British Columbia
Vancouver, BC, Canada