every org iβve worked in, around, or observed has some sort of layered process
call it βagileβ or whatever youβd like but work has to be reduced to written specifications that developers/designers/as can actually implement
applying process to your biz app clone is good
Conversation
i really like this idea of Readme-Driven Development as a straightforward concept for planning an application
you donβt need to have full SCRUM stand ups with yourself, but break down the work into something that describes what will be built
tom.preston-werner.com/2010/08/23/rea
1
1
20
another approach that iβve seen work well is user stories
this breaks down features from the perspective of the user. what will it do? how will they use it? why will they use it? what business value does it provide?
2
12
lately iβve enjoyed Shape Up from Ryan Singer which combines some underlying agile concepts with design and research approach that produces solid functional artifacts for building software
this is what we use at egghead currently basecamp.com/shapeup
2
29
iβd strongly recommend βthinking smallerβ to start. try out different processes. implement core features first
iterate
consider not trying to βclone Jiraβ and instead reverse engineer a core aspect of Jira, create a spec, user stories, wire frames, etc and implement just that
1
1
12
Replying to
Sounds like a curated guide on 'how to design and build holistic demo apps for standout dev portfolios' would be super valuable π€
That would be ideal - learning club that starts with user stories, lateral thinking, scopes out one small feature of a bigger system, implements a demo of it, then documents it really well on a personal blog. "The Anti-Todo-App Club" ;)
1
6
Show replies

