Eovendo improvements

Get Started. It's Free
or sign up with your email address
Rocket clouds
Eovendo improvements by Mind Map: Eovendo  improvements

1. Start measuring Quality

1.1. Static code anaysis

1.1.1. Sonar Cube

1.1.2. PVS Studio

1.2. QA Metrixes

1.2.1. Defect trend

1.2.2. Measure number of defect reopening per dev

1.2.3. Bug scorecard per dev (only with normal critical levels, not applicable for current severity approach)

1.3. Use normal critical levels

1.3.1. For now only Blocker and Critical levels exist. Number of issues in that statuses have to be limited as otherwise this is 'Fake' prioritization approach.

1.4. Definition of done

1.4.1. Create a dev checklist of quality attributes to be checked against completed task not to miss anything important (to be updated on regular basis)

1.5. Code review mandatory practice

1.6. Architecture audit

1.6.1. To identify stuff that "Martin is afraid to imagine" like 2 DBs for the same stuff

1.7. Introduce TDD

1.8. Always cover fixes by tests

1.9. Automated smoke suite

1.9.1. Maybe even on each Merge Request

1.10. Performance quality

1.10.1. Do we need to ensure performance is appropriate?

1.11. Security testing

1.11.1. Do we need to ensure there is no major security vulnerabilities?

1.12. Proactively validate TOP-X most important company / financial reports

1.13. Dedicated stream to rework critical modules instead of fixing never ending defects

2. Blockers

2.1. Setup automated Jira alerts eg. in blocked status more than for 5 days

2.2. Assign blockers to people responsible for unblocking (or Team lead)

2.3. Introduce mandatory weekly review of blockers

3. Priorities

3.1. Review confirmed rules violations

3.1.1. If found - to be discussed with all teammates on retrospective

3.2. Onboarding: make sure rules are properly communicated to new people

3.3. Daily: explicitly communicate next tasks (priorities)

3.4. Document violations, add scores for each dev

4. Team

4.1. Regular visits of Martin to Kyiv

4.1.1. Improve team involvement by regular syncs and sharing of vision, roadmap and key company goals

4.2. Perform regular retrospectives, focus on constant improvements

4.3. Introduce proper onboarding process

4.4. Ensure quick transition from storming to performing phase

4.5. Perform regular one-to-one meetings to minimize attrition and internal conflicts

4.6. Obey to the work discipline

4.7. Enable releases on Friday

4.7.1. To enable releases on Friday overtime rates over the weekend to be introduced

5. Scope

5.1. Introduce estimations

5.1.1. Measure velocity

5.1.1.1. Martin says that team is not becoming faster, but the feeling is not we wok with. We need to measure velocity trends and work with it accordingly - only this trend can show the ground truth of speeding or slowing down.

5.1.1.2. To enable measurement, estimations to be introduced

5.1.2. Measure scope trend

5.1.2.1. Martin claims that the number of tasks increased from 700 to 1000. It doesn't confirms that the team works slower. Team speed is quantified by velocity index. Number of tasks means that the product owner was more productive. On the other hand team has grown from 10 to 15 (150%) and the quantity of task has grown proportionally. We need to measure not just quantity of tasks but their size as well to see how the added scope is changing over the time.