- There are many methods and philosophies that describe how a team or organization should develop software.
- Teams adopt these methods and philosophies inherently or without intentional thought. Which leads them to be suboptimal in their performance.
- There is not one method that is best suited for all cases.
My goals with this research are to a.) identify and understand the individual and shared properties of each distinct method, philosophy, team, and product type in a software development context; b.) Produce recommendations on which methods and philosophies should be used with each team and product type; c.) Describe any methods and philosophies that work best together; and d.) Describe any methods and philosophies that work against each other.
- Description of Entities
- Adaptive Software Development
- Iterative and incremental development
- Behavior driven development
- Test driven development
- Chaos model
- Wheel and spoke model
- Dynamic systems development method
- Rapid application development method
- Feature driven development
- Comparison of methods
- Comparison of philosophies
- Cross reference of methods and philosophies
- Comparison of teams
- Comparison of products
- Ranked attribution of each combination
- By team type
- By product type
- Complimentary methods and philosophies
- Detrimental methods and philosophies
- Capability maturity model integration (cmmi)
- MoSCoW method
Description of Entities
This website is licensed under the MIT license © 2018 Matthew L.
Simpson | FAQ