Selecting methods

Conventional and agile project management

In conventional project management clearly defined goals are defined from the outset (SMART), and a thoroughly planned project is defined in phases with milestones. The phases (steps) of the process would be, for example, analysis, design, and implementation up the project going live.

Agile approaches (e.g. Scrum, Kanban, eXtreme Programming) stem, particularly in software projects, from a level of complexity that is far too high for things to be planned in their entirety. Thus the idea is:

• to use small development cycles of typically 30 days, to align the detailed planning to them, and to implement and finalize them in keeping with requirements
• to log requests and requirements in a product backlog, and implement them in order of priority, if necessary
• to practice close and intensive cooperation between project owner and the implementing, largely self-organizing team

A realistic approach

Is the agile approach better in principle? The answer to this question generally consists not just in the organizational structure and culture of your company, but also in the resulting attitude of employees. To a large degree agile means self-determined. Supervisors are there more as coaches than as decision-makers.

Do agile methods work at all in a conventional project environment? The answer is yes. Things don't have to be the same all the time: divergent elements can also introduce something fresh into the team, for example, and encourage creative approaches. Even a daily 15-minute stand-up meeting will increase transparency in the team, deal with problems, and promote cooperation.

A consultation session can determine which methodology is the right one for organizing your company, and which is most suitable for implementing a project.