How do you change software development methods to fit feedback?

1 Choose a flexible method

Some software development methods are more rigid and linear than others, such as the waterfall model, which follows a predefined sequence of stages from planning to deployment. These methods may not be suitable for projects that need frequent feedback and adjustments, as they can be slow, costly, and resistant to change. Instead, you may want to choose a more flexible and iterative method, such as agile, which breaks down the project into smaller and manageable units, called sprints, that deliver value to the customer and incorporate feedback along the way.

3 Adjust your scope and priorities

Feedback can affect your scope and priorities, as it may reveal new or changing customer needs, expectations, or preferences. You may need to add, modify, or remove features, functionalities, or requirements, depending on the feedback you receive. To adjust your scope and priorities, you need to be flexible and realistic, and avoid overcommitting or underdelivering. You also need to communicate and negotiate with your customer and stakeholders, and ensure that the changes are aligned with the project goals and vision.

4 Learn from feedback

Feedback is not only a source of information, but also a source of learning. You can use feedback to improve your skills, knowledge, and practices, as well as to discover new opportunities, ideas, or solutions. To learn from feedback, you need to be open-minded and curious, and avoid taking feedback personally or defensively. You also need to reflect on the feedback, and identify what worked well, what didn't work well, and what can be done better next time.

5 Evaluate your methods

Changing your software development methods to fit feedback is not a one-time event, but an ongoing process. You need to evaluate your methods regularly, and assess how well they are serving your project, your customer, and your team. You can use various criteria to evaluate your methods, such as customer satisfaction, software quality, team productivity, project performance, or feedback quality. You can also use various methods to evaluate your methods, such as surveys, interviews, reviews, metrics, or tests.

6 Experiment with new methods

Finally, changing your software development methods to fit feedback is also an opportunity to experiment with new methods, or to combine different methods, that may suit your project better. You can explore new methods that are emerging or evolving in the software industry, such as lean, devops, or kanban, or that are specific to your domain, such as game development, web development, or mobile development. You can also mix and match different methods, or create your own hybrid method, that best fit your project needs, goals, and context.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?