3 ms·
Agile Value: Individuals and interactions over processes and tools DIB Mapping: “Competence trumps process” This makes sense to me, that said: how do you comm
by tegiddrone 4y ago
Agile Value: Individuals and interactions over processes and tools
DIB Mapping: “Competence trumps process”
This makes sense to me, that said: how do you commodify competence? I'm thinking about the teams I've worked with that do agile but wind up writing an objectively difficult-to-maintain codebase because they lack competency in anything that resembles best practices. I will commend the teams for shipping large products and doing agile though.
- kqr 4y agoThe question you ask is basically "how to get good at developing software?" The key components are (a) exposure to a wide variety of circumstances that require new skills, and (b) appropriate feedback on performance. Some practical ways to achieve this: - Allow people to make mistakes and fail in a safe social environment. Even if you watch the intern as they are about to reboot the prod database, see what happens. I bet you they will learn something -- and so will you! - Staff teams with a majority of experienced developers (at the very least 5 years, ideally 10 or 15). - Have developers operate the software in production. - Encourage a high bar in code review. - Involve the same developers from start to finish (initial prototype, first production version, maintenance period, sunsetting) of a product. - Embed useful metrics for availability, performance, resource usage, etc.