some intro
Although some organizations still have a one track mind about the methodology that is used in their software development projects, in which case it all comes down to using a linear methodology, most will use a multi-methodology approach. In this case the big question for a starting project is: which methodology suits my project best?
In most projects the choice is three-fold:
- Linear. Many traditional software development, including many SAP and BI projects, is still executed using a waterfall styled, linear approach. These approaches are characterized by having very strict milestones, and different stages per discipline, such as information analysis, functional design, technical design, development and testing. Each of these stages is executed only once, leading to a complete and accurate milestone deliverable. Any changes that might - and will - occur, are treated as change requests, and provided for after the original project has ended.
- Architectured. There are also companies that use fully described iterative methodologies, such as Rational Unified Process (RUP), Cathalysis or Select Perspective. Such methodologies are best described as a wide variety of roles, deliverables, stages, activities, and best practices, that support iterative development, but are far too often executed in a waterfall style.
- Agile. A fast growing number of companies, or projects within companies, evangelise the use of an agile methodology. Good examples of such methodologies are Scrum, extreme programming (XP), Smart, Evo or Feature Driven Development (FDD). These more recent methodologies all focus around working in very short iterations (for example of two to four weeks), delivering working software as fast as possible, and most important allowing for change in requirements and software during the project. This flexibility is possible due to constant prioritization and having a small unit of work.
Criteria:
When choosing tools, platforms etc. We set up criteria and try to make our choice binary, it is either this or that and there is no in between. In trying to position methodologies we also use some basic criteria. But we only use this to give direction and guidance. We are not making a binary decision. In choosing a methodology there is no right or wrong, there is only a best fit. This actually can mean that when choosing a waterfall-like methodology you can even use aspects of other methodologies to enrich your way of working.
So, for the sake of simplicity we use two main criteria:
1. Critical (y-axes)
2. Size (x-axes)
- Effective Communication
- complexity
- Team size
- fixed requirements?
Model with image!
Steps:
- pick a methodology type that suits you
- pick a methodology in this category
- tailor the methodology
Be aware that:
- add considerations
RH.