/
Retrospective Hackathon V5 Leipzig

Retrospective Hackathon V5 Leipzig


Date
Participants

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

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