Do your work and software development processes fit?

Project leads often only differentiate between Agile, Hybrid or Classic project management approaches. However, the decisions around software development (testing, code review, story acceptance, CI, CD etc.) need to be considered in unison.

Does your company culture fit to your agile framework?

Many agile frameworks such as Kanban or Scrum build upon a sentiment of ownership and agency, meaning that team members accomplish their tasks responsibly and proactively. Yet, many corporate cultures struggle with these very same attributes.

Do scaled Agile frameworks moderate Product Management?

When multiple teams are developing a product, Product Management (PM) needs to step to the fore, communicating business requirements, defining scopes, addressing dependencies etc. At their core, SAFe & Co merely provide a structure around PM.

Is Agile about ad-hoc changes to requirements & software?

Agile is much-misunderstood. Requirements change fast in Today's world and so software needs to adapt, too. Still, in every project there are KNOWN requirements and those that are UNKNOWN. Competent management specifies the former up-front.

What is the relationship between Agile and formalization?

Agile understands that user-centered and fast-paced Software Development requires a prioritization of effective informal communication. Therefore, it implements structures and processes only as required, depending on the natural proclivities of the team.