Hey people at Zygor,
Let's start at the start.
I'm a developer (senior dev & teamlead) as profession and have been working with different languages and workflow philosophies for quite some time (~15 years).
Working on (mostly) NodeJS infrastructures with Angular frontends on an Agile Scrum workflow and a (private) git-flow repository system, continues integration and DTAP.
Because I work with these kind of systems/flows/ideas on a daily basis and see the merits of those structures named above, it got my wondering how you guys approach problems from a developers perspective.
Do you work in sprints with epics, stories, task, storypoints and the whole bunch? Or do you work more like a general issue board and pick up whichever happens to have the most (internal) votes.
I'd love to hear from you guys on this as you also have a potentially short release cycle, which can make things tricky at times.
Greetings from a fellow dev.
/wave
Let's start at the start.
I'm a developer (senior dev & teamlead) as profession and have been working with different languages and workflow philosophies for quite some time (~15 years).
Working on (mostly) NodeJS infrastructures with Angular frontends on an Agile Scrum workflow and a (private) git-flow repository system, continues integration and DTAP.
Because I work with these kind of systems/flows/ideas on a daily basis and see the merits of those structures named above, it got my wondering how you guys approach problems from a developers perspective.
Do you work in sprints with epics, stories, task, storypoints and the whole bunch? Or do you work more like a general issue board and pick up whichever happens to have the most (internal) votes.
I'd love to hear from you guys on this as you also have a potentially short release cycle, which can make things tricky at times.
Greetings from a fellow dev.
/wave
Comment