/
Retrospective Hackathon
Retrospective Hackathon
Retrospective
What did we do well?
- We operate as team
- Helpful/friendly/positive attitude of team members
- Requirements are comprehensive
- Developer introduction
- Dev meeting
- Tshirts
- Micro-service templates
- Help with questions
- Many communication channels
What should we have done better?
- Decision-making
- Dev meeting - length of discussion
- Task granularity
- React-flux is difficult technology
- Tech introduction
- Dev blog
- Test automation
- We need real users to test
Actions
- Benjamin Wulff Decisions via mailinglist
- Benjamin Wulff Klaas Andries de Graaf JIRA gardening
- Klaas Andries de Graaf Benjamin Wulff More dev/tech intro & resources
- Benjamin Wulff Writes dev blog
- Testing after September release
, multiple selections available,
Related content
2017-02-24 Retrospective Hackathon V3 Amsterdam
2017-02-24 Retrospective Hackathon V3 Amsterdam
More like this
Retrospective Hackathon V5 Leipzig
Retrospective Hackathon V5 Leipzig
More like this
Knowledge Spreading
Knowledge Spreading
More like this
Use of testing VMs
Use of testing VMs
More like this
CI to Stable - procedures and testing
CI to Stable - procedures and testing
More like this
Quality in Use report Jan 2018: Identified issues and recommendations
Quality in Use report Jan 2018: Identified issues and recommendations
More like this