3 ms·
> every sprint we either fail to deliver the work we commit to Are you committing too much volume? Too much complexity? You say that half the team is quite ju
by joshmn 6y ago
> every sprint we either fail to deliver the work we commit to
Are you committing too much volume? Too much complexity?
You say that half the team is quite junior: I have found that junior developers often have a more difficult time judging how long something will take more than they do actually shipping a feature. They haven't been through the weeds like senior developers so they don't have that experience of "okay, well this can go wrong this many ways" yet.
> deliver work that ultimately fails the QA process
Hearing this makes me think that it's a complexity problem, tied in with bad estimates.
It sounds like you're committing to too much complexity and doing that with too much volume. Reduce scope, reduce volume and I think you will see better results.
- user5994461 6y agoAgreed. I will add that juniors must be taught to test. In my experience they always think that they need to ship, especially when the manager is pushing and setting deadline. The job of the developers is to deliver working software (this involves testing), not to ship code ASAP. You test before shipping. Do not deliver something that's not been tested, if you don't have time to test you don't ship, shipping can always wait. Makes me wonder if there is a deeper issue with the environment (testing tools? business complexity?). Complexity should be reasonable, we're talking startup from scratch, not 10 years old legacy code? Can they run locally? Do they have test data and a test environment?