methodology

methodology

Waterfall or agile or a bit of everything?
The selection of the appropriate approach for a project is essential for the success of the project. Whether classic waterfall or fully agile, each method has its justification and needs its specific requirements in order to be successful. At heart, project managers are agile, because successful delivery (in time, in budget, in quality) is the primary goal. Methodology is a means to an end - a tool kit that helps us achieve our goal. "Tayloring", ie the adaptation of a method to the specific project situation, is a must at the start of the project.
Backlog: The backlog does not always come from the head of a product owner, but has to be worked out in a preliminary phase (explore). This phase includes a view of the E2E processes and how they run across different applications. The target image to be created for an overall architecture. Because only clear and precise backlog items can be implemented by the Scrum teams. "Shipable software" per sprint: We will not be able to deliver a "releasable product increment" after a sprint for highly integrated applications, especially in the banking sector. So what! Nevertheless, it is recommended to use as many agile elements as possible. From "releasable in production" becomes "releasable into system integration test". For SAP projects, SAP Activate is recommended as a hybrid project approach.
  • Voll Agil

    Button
  • Image title

    auch irgendwie agil

    Button
  • Image title

    So Agil wie möglich!

    Button
  • Image title

    Der richtige Methoden-Mix ist entscheidend!

    Button
Share by: