As I said before, just about everybody who participates in the software development life cycle (SDLC) wants to do their “best”, and will, if given the opportunity. But if each individual’s “best” is attributed to internalized motivations, how do you provide each individual the opportunity to do their “best”? First, you have to find out what they care about. That is why I built Strong(ER).
Strong(ER) is a tool that assesses what you care about in the SDLC and then coaches you how to apply your individual strengths to do more of what you love to do. As coaches and managers, this information is vital to us as we develop our people and build our teams. Because in order to produce the highest quality software, it is essential that at least one member on the product team cares deeply about each of the following:
Someone who cares deeply about Business Value is internally motivated to develop products that create more than enough revenue to support business goals. Vital Decisions: product feature selection, product roadmap planning, product pricing strategies, etc.
Someone who cares deeply about System Value is internally motivated to bring into being systems that accurately deliver requested business value. Vital Decisions: selection and implementation of elicitation techniques, requirements analysis (INVEST), acceptance testing, etc.
Someone who cares deeply about Process Performance is internally motivated to execute project schedules on time and on budget. Vital Decisions: schedule planning, resource planning, feature trade-off negotiations, etc.
Someone who cares deeply about Application Architecture is internally motivated to make sure the systems they are responsible for are maintainable, modifiable, reusable, and understandable – you get the picture. Vital Decisions: component design, database design, implementation modeling, etc.
Someone who cares deeply about System Quality is internally motivated to make sure the systems they are responsible for are secure, trustworthy, and perform as expected. Vital Decisions: test planning, test execution, test reporting, test tool selection, etc.
Someone who cares deeply about Development Process is internally motivated to make sure the people they are responsible for have what they need to do their jobs well. Vital Decisions: process selection, process adoption strategies, process tool selection, etc.
Someone who cares deeply about Implementation is internally motivated to make sure their source code is free from defects, easy to understand and change, and is as efficient as possible. Vital Decisions: algorithm creation, unit testing strategies, documentation strategies, etc.
Someone who cares deeply about Technical Architecture is internally motivated to make sure the systems they are responsible for make use of the most capable computer technologies possible. Vital Decisions: language selection, database selection, deployment strategies, 3rd party component selection, hardware selection, etc.
Someone who cares deeply about User Experience is internally motivated to make sure the users they are responsible for can be as productive as possible using the systems in their environments. Vital Decisions: user experience modeling, UI and graphics design, usability testing, etc.