Agile Experiences

Agile Experiences


Scrum is the industrial standard to create and develop awesome digital products.


Scrum is a minimalist framework empowering your organization to deliver digital products.

  • Scrum is an additive framework. Please be pragmatic and professional.

    • Roles: Product Owner, Scrum Master, Team Member

    • Events: Sprint, Sprint Planning, Daily Scrum, Review, Retrospective, Backlog Refinement

    • Artifacts: Product Increment, Product Backlog, Spring Backlog, Definition of Done

  • Technical Agile and Scrum

  • Product Development

  • Good Practices

  • Anti-Patterns: Definition of Ready, Project Leader, Milestones, Quality Group, Undone Work

Scrum and LeSS provide proven approaches and good practices how to efficiently work on one product line with five to hundreds of product developers.

Product Development

A successful digital product shall fulfill customers' expectations.

  • Roadmap with a horizon of maximum 2 years

  • Release Plan with a horizon of maximum 1 year

  • Stakeholder Map is crucial for onboarding

  • Risk Management

  • Customer Journey and Design Thinking

  • Story Mapping

  • Usability

  • Legal Aspects

Technical Agility

Success with Scrum is often determined how fluent your software development teams are with technical agility. In the end, you shall deliver a working piece of software delighting your customers.

  • Software Craftsmanship [1, 2]

  • Software Engineering [3, 4, 5]

  • DevOps: Continuous Integration, Continuous Delivery, Continuous Deployment, Git, Living Documentation, Automated Quality Insurance

  • Clean Programmer [6, 7, 8, 9, 2]

  • Evolutive Architectures [10, 11, 12]

  • Fitness Functions [10]

  • Documentation Good Practices

Continuous Improvements


[1] S. Mancuso, The Software Craftsman. Prentice Hall, 2015 [Online]. Available:

[2] R. C. Martin, Clean Craftsmanship. Addison-Wesley Professional, 2021 [Online]. Available:

[3] D. Farley, Modern Software Engineering. Pearson Education, Limited, 2022 [Online]. Available:

[4] T. Winters, T. Manshreck, and H. Wright, Software Engineering at Google : Lessons Learned from Programming Over Time. O’Reilly Media [Online]. Available:

[5] R. L. Glass, Facts and Fallacies of Software Engineering. Addison-Wesley Professional, 2002 [Online]. Available:

[6] R. C. Martin, Clean Code. Prentice Hall, 2009 [Online]. Available:

[7] R. C. Martin, The Clean Coder. Prentice Hall, 2011 [Online]. Available:

[8] R. C. Martin, Clean Agile. Prentice Hall, 2020 [Online]. Available:

[9] R. C. Martin, Clean Architecture. Pearson, 2017 [Online]. Available:

[10] N. Ford, R. Parsons, and P. Kua, Building Evolutionary Architectures: Support Constant Change, First. O’Reilly Media, 2017 [Online]. Available:

[11] M. C. Feathers, Working Effectively with Legacy Code. Prentice Hall, 2004 [Online]. Available:

[12] L. Hohmann, Beyond Software Architecture. Addison-Wesley Professional, 2003 [Online]. Available: