/
Retrospective Hackathon V5 Leipzig
Retrospective Hackathon V5 Leipzig
Retrospective
What did we do well?
Process
- Incremental improvements of the features
- Deployment has been improved as a tool and process
People
- A good teamwork atmosphere
- Work well as a team
- Open-minded team
Communication & tools
- Communication tools and process
- Very good infrastructure for development
- Project review meetings
- Conversational tone/politeness in communication
- Themed (seasonally or otherwise) developer meetings
- Linux is great
Goal/Focus
- Presentation rooms are really cool
What should we have done better?
Process
- Not many people in Front-end (slide editor) + back-end systems integration.
- It is hardest now to make progress + time for planning as SlideWiki has become more complex
- Having a procedure for situations when there are no volunteers for a certian task (ticket)
- 1 month sprints too long - we should be able to better PLAN then → what's in gets done
- Ensure QA before merge
- Please test you code!
Goal/Focus
- More focus on graphic design rather than accessibility
- Responsive interface for mobile devices
- More research work
- More semantics to be implemented
Communication & tools
- Information at too many different places (Google-Doc, Confluence, JIRA, Slack)
- Hard to know who to contact about specific parts of the codebase
- Linux is great
Suggested Improvements retrospective participants
Communication
- Documentation
- Changelogs / release notes for releases
- Demo during dev telco
Process
- Time for planning + design
- Proportionally split responsibilities for open tasks (e.g., performance)
- A clear process for updating/synchronizing our different servers
- Database maintenance - fix schema + data changes
- Tests everywhere
Goal/focus
- More focus on core functionality to encourage users
- Have proper roadmap
- More research/publications
- more stand-alone applications built on top of services
People
- Become creative
Tools
- Backup & reliability of the servers
Actions
- Documentation
- Consider planning poker? Quick app for this?
- Have greater overlap / concurrent work during testing → have testing/release/deployment and planning together.
- Ask trial partners to do testing - offload dev team
Actions after retrospective hackathon V3 Amsterdam
- Documentation on how to deploy SlideWiki, also for OSS dissemination/support (Kurt Junghanns Roy Meissner do you want to publish/extend the existing guide on the on developers blogs http://tinyurl.com/zpme2lh We can possibly also add materials from a tutorial on using docker during WebSci if it is accepted)
- More knowledge spreading presentations (Benjamin Wulff Klaas Andries de Graaf )
- Retrospectives more often (Klaas Andries de Graaf Benjamin Wulff )
- Developer documentation with worked out examples, also for OSS dissemination/support (on developers blogs? Kurt Junghanns Former user (Deleted) - can you link to this Prezi http://tinyurl.com/hzl3y6l on the developers blog? This is some documentation/example on how to use the flux and react architecture that I (Klaas Andries de Graaf) presented during Hackathon V1. Also, shall I make a post summarizing and combining http://tinyurl.com/zlq9wcy and http://tinyurl.com/z7o3eh4 and http://tinyurl.com/zw7buun for new devs and/or OSS people that want to join the project?)
- Peer code reviews → assign more people to PR's yourself. (All!)
- Add more code comments (All!)
- Frequent reminders about knowledge spreading presentations (Ben)
- Make Documentation part of QA? (Ben)
, multiple selections available,
Related content
2017-02-24 Retrospective Hackathon V3 Amsterdam
2017-02-24 Retrospective Hackathon V3 Amsterdam
More like this
Retrospective Hackathon
Retrospective Hackathon
More like this
Target outcome (Statistics)
Target outcome (Statistics)
More like this
Knowledge Spreading
Knowledge Spreading
More like this
Leipzig trial feedback
Leipzig trial feedback
More like this
Trial requirements from April 2017 Plenary (RQM - ReQuirement Madrid)
Trial requirements from April 2017 Plenary (RQM - ReQuirement Madrid)
More like this