Successful software-development teams need to strike a balance
between quickly delivering working
software systems, satisfying stakeholders, and addressing risks.
Their challenges are further compounded as they strive to
improve and introduce new ideas and ways of working.
Essence was the very first step on a journey to revolutionize
software engineering. A common ground was needed to build the
future upon. The Essence™ standard was created in 2014 by the Software Engineering
Methods and Theory (SEMAT) and Object Management
provide a universal language for defining methods and practices
common to all software engineering.
Essence intuitively describes the essential elements of any
software development and helps teams understand where they are,
what's missing or what needs to be addressed. Essence is
method-agnostic and unites the myriad of disconnected,
conflicting, costly, contradictory and transitory methods and
practices that exist in most large organizations.
Essence helps practitioners (e.g., architects, designers,
developers, testers, developers, requirements engineers, process
engineers, project managers, etc.) compare methods and make
better decisions about their practices.
Essence helps organizations:
- Create a common ground for the discussion, improvement,
comparison, and sharing of their software engineering
methods and practices
- Unlock large methods and create modular practices that can
be independently selected and applied
Create 'pluggable' practices from different sources that can
be plugged together to form a new adaptable way-of-working
- Build extensible practice libraries that will evolve and
grow organically over time
- Clearly assess team progress and help teams understand
where they are, what they should do next, and where they
need to improve
- Understand the health and progress of any software
endeavors regardless of the practice or methodology being
- Meet regulatory and compliance requirements as disparate
practices and methods are now transparent and work together