agile - software methodology used in project -

agile - software methodology used in project -

currently working on porting benchmark application system. working alone, frustrated software methodology have use. please give me ideas.

i going assume you're wondering agile approach utilize on project tagged question accordingly.

agile about:

delivering working software continuously , regularly aiming @ technical excellence , avoiding technical debt improving way work , retrospecting regularly

i'd whatever use, own approach software development, if can check 3 items list, you're pretty much agile me. people need strict guidelines , artifacts , that's fine, help people become agile far beingness mandatory despite dogmas out there.

here's how approach situation.

take step , seek identify of import features or abilities of benchmarking application. important, mean features people using in end cannot live without. 1 time have list of those, set them on post-it notes, index cards, trello, jira or whatever tool want use.

split each of features full-stack chunks of functionality business driven. i'm not talking technical tasks here, smaller features usable actual people. opt "grandma driven" approach here, asking myself "would grandma able understand i'm trying do?". it's create sure i'm focusing on total stack feature , not technical task "populate database". 1 way see applying dimensional planning each of features identified (http://www.xpday.net/xpday2007/session/dimensionalplanning.html).

set iteration length (i go 1 or max 2 weeks when i'm working alone) , work 1 little item @ time. don't write code later, need solve problem @ hand. quality not option. focus on coding , testing practices.

at end of iteration, check how many features implemented , set number somewhere on chart, in google spreadsheet or whatever. help see if you're on track. feedback colleagues or potential users of scheme , reflect on feedback. it's not because you're porting platform can't create better.

if end not having little plenty granularity what's left or not plenty stuff in list of things do, spend time repeating steps 1 3.

at end of each iteration, maintain tracking how many items did see if still have plenty pace. if not, inquire why , alter in way work or help. again, main focus create progress , deliver software works @ end of each iteration.

it might not reply question , know didn't give reply of type, utilize kanban, scrum or whatever believe it's not appropriate in specific case , generate overhead , boredom you.

hope helps anyway, luck project.

project agile methodology