Please enable JavaScript.
Coggle requires JavaScript to display documents.
Insync Workflow (Feedback received (One-off Questions
Support asks a…
Insync Workflow
Feedback received
One-off Questions
- Support asks a quick question in #support channel
Dev answers in Slack
- Average response time: ~20hrs
-
Issue creation
Dev response
- Average response time (Github): ~7 days
- Follow-up response time: ~15days
Proposed solution
- Tag the dev on triage and msg them on Slack
Additional Reports
- Average time for reports to come in in current version: ~3 weeks #
Prioritization level changes
- Timeframe for change on initial level: ~20 days
-
-
Monthly Planning
- Priority features are laid out
- Priority issues are determined
- Backlogs from previous month
- Ongoing development status
Dev Sprint Planning
- High level plans are presented
- Devs lay out their tasks for the sprint
- Priority 0 issues are brought up
Points for improvement
- Tasks are selected by the devs themselves - there are tasks which are left with no assigned devs to work on
- Most issues are not given any dev assignment
- Know the estimates for the tasks included for better scheduling of releases
Bi-Weekly sprint planning
- Devs make their task plans known
- All dev tasks are selected by the devs themselves except when a critical task comes in
Points for improvement
- Tasks being worked on can be adjusted without the knowledge of planning manager
- Work estimates are not clearly defined by the devs for each task therefore, the planning manager cannot make rough estimates on tasks for devs which will be useful for setting monthly planning schedules as not all devs are included in the monthly planning
- Sometimes high level overviews are too high given the task at hand i.e. tasks that has a wide coverage
- No explicit target milestone on each tasks during meetings
Development Week 1
Alpha Internal Release
- Thoroughly tested especially when new features are included
- Newly developed features are included
- Feature testing is done
Mid-sprint checkpoint
- Tasks being worked on are presented by the devs
- KT sessions are included in tasks
Points for improvement
- Tickets which can't make it to the release should ALWAYS be mentioned so the more senior devs can help out
Development Week 2
RC Release
- Thoroughly tested especially when new features are included
Critical bugs found?
- 2 more items...
Sprint retrospective
- Pain points during development
- Accomplishment/milestone checking
- Plans to improve
- 1 more item...
-
-