Just as human DNA captures our essential nature, so too Essence captures the essential nature of software engineering.

Essence is a language for defining methods and practices common to all software engineering. Essence was created by Software Engineering Method and Theory (SEMAT) and approved by The Object Management Group as a standard in 2014.

SEMAT

It stands for Software Engineering Method and Theory, the initiative was launched in December 2009 by Ivar Jacobson, Bertrand Meyer, and Richard Soley with a call for action statement and a vision statement.

The purpose of SEMAT is to bring the rigor of engineering discipline back into software development. If the project involves developing a driverless car or a health monitoring systems based on Artificial Intelligence (AI) it is important that failure modes are considered as part of the design, the boundary conditions, reliability and critical to quality (CTQ) parameters.

SEMAT can help in bridging the gap between current methods and theory.

Essence

The most interesting part that caught my attention while studying SEMAT was "Essance" - it is the kernel or a foundation on top which any method or framework can be expressed. It is based on three principles. it is actionable; it is extensible, and it is practical.

The kernel provides a simple language to express methods and practice, in line with the three principles.

"being" and Agile

This is the topic close to my heart, exploring the world of being. I'm exploring the "being" part of "being Agile"

This takes me back to study of Ontology (I have written blogs and spoken at Global Scrum Gathering and in Capability Counts conference on this topic), It is a branch of philosophy(in particular meta-physics) focusing on study and nature of ‘being’, this term is also widely used in social science, computer science /artificial intelligence, information science and in many other fields.

The term is derived from Greek words, “Onto” for existence and “logia” for study, science. The Latin derivative ontologia means science of being.

In general, ontology focuses on nature of 'being'. For example, let’s consider an apple. The existence of apple can be experienced by sight, touch, smell, and taste. In an apple juice, though the form is changed the existence can be experienced in the form of smell and taste. The “essence” or the being of an apple can be experienced.

In the case of living beings the concept of “being” is different, especially for human beings. Human beings have a wide range of 'beings' in which they express themselves. Normally they are expressed as emotions like “being happy”, “being sad”, “being angry”, “being enthusiastic” and so on. The being is not just the emotional state but it is much more than that. It is a combination of mental state (attitude and state of mind), emotional state (feelings and emotions), bodily state (body sensation), thoughts and thought process (logic and memory) in a given moment of time or in a given situation.

This also includes mind-set (frame of reference) and worldview (model of reality).

In fact, one can’t write/read about “being” then it becomes “knowing”.

Endnote

There is a work to be done to express all these ideas as well to study the existing methods and theory. The concept of common ground and Kernel is fundamental and fascinating, it helps to connect the dots with so many interesting topics.

Just as human DNA captures our essential nature, so too Essence captures the essential nature of software engineering.

Essence is a language for defining methods and practices common to all software engineering. Essence was created by Software Engineering Method and Theory (SEMAT) and approved by The Object Management Group as a standard in 2014.

SEMAT

It stands for Software Engineering Method and Theory, the initiative was launched in December 2009 by Ivar Jacobson, Bertrand Meyer, and Richard Soley with a call for action statement and a vision statement.

The purpose of SEMAT is to bring the rigor of engineering discipline back into software development. If the project involves developing a driverless car or a health monitoring systems based on Artificial Intelligence (AI) it is important that failure modes are considered as part of the design, the boundary conditions, reliability and critical to quality (CTQ) parameters.

SEMAT can help in bridging the gap between current methods and theory.

Essence

The most interesting part that caught my attention while studying SEMAT was "Essance" - it is the kernel or a foundation on top which any method or framework can be expressed. It is based on three principles. it is actionable; it is extensible, and it is practical.

The kernel provides a simple language to express methods and practice, in line with the three principles.

"being" and Agile

This is the topic close to my heart, exploring the world of being. I'm exploring the "being" part of "being Agile"

This takes me back to study of Ontology (I have written blogs and spoken at Global Scrum Gathering and in Capability Counts conference on this topic), It is a branch of philosophy(in particular meta-physics) focusing on study and nature of ‘being’, this term is also widely used in social science, computer science /artificial intelligence, information science and in many other fields.

The term is derived from Greek words, “Onto” for existence and “logia” for study, science. The Latin derivative ontologia means science of being.

In general, ontology focuses on nature of 'being'. For example, let’s consider an apple. The existence of apple can be experienced by sight, touch, smell, and taste. In an apple juice, though the form is changed the existence can be experienced in the form of smell and taste. The “essence” or the being of an apple can be experienced.

In the case of living beings the concept of “being” is different, especially for human beings. Human beings have a wide range of 'beings' in which they express themselves. Normally they are expressed as emotions like “being happy”, “being sad”, “being angry”, “being enthusiastic” and so on. The being is not just the emotional state but it is much more than that. It is a combination of mental state (attitude and state of mind), emotional state (feelings and emotions), bodily state (body sensation), thoughts and thought process (logic and memory) in a given moment of time or in a given situation.

This also includes mind-set (frame of reference) and worldview (model of reality).

In fact, one can’t write/read about “being” then it becomes “knowing”.

Endnote

There is a work to be done to express all these ideas as well to study the existing methods and theory. The concept of common ground and Kernel is fundamental and fascinating, it helps to connect the dots with so many interesting topics.

Just as human DNA captures our essential nature, so too Essence captures the essential nature of software engineering.

Essence is a language for defining methods and practices common to all software engineering. Essence was created by Software Engineering Method and Theory (SEMAT) and approved by The Object Management Group as a standard in 2014.

SEMAT

It stands for Software Engineering Method and Theory, the initiative was launched in December 2009 by Ivar Jacobson, Bertrand Meyer, and Richard Soley with a call for action statement and a vision statement.

The purpose of SEMAT is to bring the rigor of engineering discipline back into software development. If the project involves developing a driverless car or a health monitoring systems based on Artificial Intelligence (AI) it is important that failure modes are considered as part of the design, the boundary conditions, reliability and critical to quality (CTQ) parameters.

SEMAT can help in bridging the gap between current methods and theory.

Essence

The most interesting part that caught my attention while studying SEMAT was "Essance" - it is the kernel or a foundation on top which any method or framework can be expressed. It is based on three principles. it is actionable; it is extensible, and it is practical.

The kernel provides a simple language to express methods and practice, in line with the three principles.

"being" and Agile

This is the topic close to my heart, exploring the world of being. I'm exploring the "being" part of "being Agile"

This takes me back to study of Ontology (I have written blogs and spoken at Global Scrum Gathering and in Capability Counts conference on this topic), It is a branch of philosophy(in particular meta-physics) focusing on study and nature of ‘being’, this term is also widely used in social science, computer science /artificial intelligence, information science and in many other fields.

The term is derived from Greek words, “Onto” for existence and “logia” for study, science. The Latin derivative ontologia means science of being.

In general, ontology focuses on nature of 'being'. For example, let’s consider an apple. The existence of apple can be experienced by sight, touch, smell, and taste. In an apple juice, though the form is changed the existence can be experienced in the form of smell and taste. The “essence” or the being of an apple can be experienced.

In the case of living beings the concept of “being” is different, especially for human beings. Human beings have a wide range of 'beings' in which they express themselves. Normally they are expressed as emotions like “being happy”, “being sad”, “being angry”, “being enthusiastic” and so on. The being is not just the emotional state but it is much more than that. It is a combination of mental state (attitude and state of mind), emotional state (feelings and emotions), bodily state (body sensation), thoughts and thought process (logic and memory) in a given moment of time or in a given situation.

This also includes mind-set (frame of reference) and worldview (model of reality).

In fact, one can’t write/read about “being” then it becomes “knowing”.

Endnote

There is a work to be done to express all these ideas as well to study the existing methods and theory. The concept of common ground and Kernel is fundamental and fascinating, it helps to connect the dots with so many interesting topics.

Steve is very shy and withdrawn, invariably helpful but with little interest in people or in the world of reality. A meek and tidy soul, he has a need for order and structure, and a passion for detail.

Is Steve more likely to be a librarian or a farmer? (Place Washington DC, USA)

Before you proceed, pause for a moment and make your choice - A for librarian and B for the farmer and also make a mental note for your reasoning. The point is not about finding the right answer but to develop an awareness about your own decision-making process. Your decisions must be based on economics (SAFe principle #1, FLOW - Principles of Product Development Flow).

This is very important especially if you are a product designer, manager or owner. These roles have a very important role to play in making decisions for the product.

If your choice is A, Librarian then it is wrong.

In this talk, we will explore some concepts of cognitive bias and Nudge from behavioural economics in the context of product development. Some of these aspects were considered as part of the during my work with Jaguar Land Rover (electrified power train project i-PACE project)

Now why the choice A (Librarian) is wrong, This is an interesting example of a heuristic bias. While making the decision we forget to consider the overall population of farmers and librarians. The description “a meek and tidy soul, he has a need for order and structure” flips the decision towards librarian for most people.

This depends on occupational stereotypes while ignoring “equally relevant statistical considerations.” The question is supposed to illustrate the shallowness of our intuitions about probability. “Did it occur to you that there are more than 20 male farmers for each male librarian in the United States? Because there are so many more farmers, it is almost certain that more ‘meek and tidy’ souls will be found on tractors than at library information desks.”

The related topic on this is NUDGE, which consists of design of choice architecture.

It is based on

INCENTIVES -

Understanding Mappings

Defaults

Give feedback

Expect error

Structure Complex choices

A properly (ethically) designed system can benefit society. (Like auto-enrolment for pension funds in UK)

Footnote:

1.
This topic is the outcome of pioneering work done two Nobel laureates - Daniel Kahneman (2002 Nobel Memorial Prize in Economic Sciences. for his work on the psychology of judgment and decision-making,) and Richard Thaler (2017 Nobel Memorial Prize in Economic Sciences for his contributions to behavioural economics.).

2.

These concepts are extensively used by many digital / social media companies. There are also ethical consideration in applying these concepts.

Steve is very shy and withdrawn, invariably helpful but with little interest in people or in the world of reality. A meek and tidy soul, he has a need for order and structure, and a passion for detail.

Is Steve more likely to be a librarian or a farmer? (Place Washington DC, USA)

Before you proceed, pause for a moment and make your choice - A for librarian and B for the farmer and also make a mental note for your reasoning. The point is not about finding the right answer but to develop an awareness about your own decision-making process. Your decisions must be based on economics (SAFe principle #1, FLOW - Principles of Product Development Flow).

This is very important especially if you are a product designer, manager or owner. These roles have a very important role to play in making decisions for the product.

If your choice is A, Librarian then it is wrong.

In this talk, we will explore some concepts of cognitive bias and Nudge from behavioural economics in the context of product development. Some of these aspects were considered as part of the during my work with Jaguar Land Rover (electrified power train project i-PACE project)

Now why the choice A (Librarian) is wrong, This is an interesting example of a heuristic bias. While making the decision we forget to consider the overall population of farmers and librarians. The description “a meek and tidy soul, he has a need for order and structure” flips the decision towards librarian for most people.

This depends on occupational stereotypes while ignoring “equally relevant statistical considerations.” The question is supposed to illustrate the shallowness of our intuitions about probability. “Did it occur to you that there are more than 20 male farmers for each male librarian in the United States? Because there are so many more farmers, it is almost certain that more ‘meek and tidy’ souls will be found on tractors than at library information desks.”

The related topic on this is NUDGE, which consists of design of choice architecture.

It is based on

INCENTIVES -

Understanding Mappings

Defaults

Give feedback

Expect error

Structure Complex choices

A properly (ethically) designed system can benefit society. (Like auto-enrolment for pension funds in UK)

Footnote:

1.
This topic is the outcome of pioneering work done two Nobel laureates - Daniel Kahneman (2002 Nobel Memorial Prize in Economic Sciences. for his work on the psychology of judgment and decision-making,) and Richard Thaler (2017 Nobel Memorial Prize in Economic Sciences for his contributions to behavioural economics.).

2.

These concepts are extensively used by many digital / social media companies. There are also ethical consideration in applying these concepts.

Steve is very shy and withdrawn, invariably helpful but with little interest in people or in the world of reality. A meek and tidy soul, he has a need for order and structure, and a passion for detail.

Is Steve more likely to be a librarian or a farmer? (Place Washington DC, USA)

Before you proceed, pause for a moment and make your choice - A for librarian and B for the farmer and also make a mental note for your reasoning. The point is not about finding the right answer but to develop an awareness about your own decision-making process. Your decisions must be based on economics (SAFe principle #1, FLOW - Principles of Product Development Flow).

This is very important especially if you are a product designer, manager or owner. These roles have a very important role to play in making decisions for the product.

If your choice is A, Librarian then it is wrong.

In this talk, we will explore some concepts of cognitive bias and Nudge from behavioural economics in the context of product development. Some of these aspects were considered as part of the during my work with Jaguar Land Rover (electrified power train project i-PACE project)

Now why the choice A (Librarian) is wrong, This is an interesting example of a heuristic bias. While making the decision we forget to consider the overall population of farmers and librarians. The description “a meek and tidy soul, he has a need for order and structure” flips the decision towards librarian for most people.

This depends on occupational stereotypes while ignoring “equally relevant statistical considerations.” The question is supposed to illustrate the shallowness of our intuitions about probability. “Did it occur to you that there are more than 20 male farmers for each male librarian in the United States? Because there are so many more farmers, it is almost certain that more ‘meek and tidy’ souls will be found on tractors than at library information desks.”

The related topic on this is NUDGE, which consists of design of choice architecture.

It is based on

INCENTIVES -

Understanding Mappings

Defaults

Give feedback

Expect error

Structure Complex choices

A properly (ethically) designed system can benefit society. (Like auto-enrolment for pension funds in UK)

Footnote:

1.
This topic is the outcome of pioneering work done two Nobel laureates - Daniel Kahneman (2002 Nobel Memorial Prize in Economic Sciences. for his work on the psychology of judgment and decision-making,) and Richard Thaler (2017 Nobel Memorial Prize in Economic Sciences for his contributions to behavioural economics.).

2.

These concepts are extensively used by many digital / social media companies. There are also ethical consideration in applying these concepts.

Steve is very shy and withdrawn, invariably helpful but with little interest in people or in the world of reality. A meek and tidy soul, he has a need for order and structure, and a passion for detail.

Is Steve more likely to be a librarian or a farmer?

Before you proceed, pause for a moment and make your choice – A for librarian and B for farmer and also make a mental note for your reasoning.

The description “a meek and tidy soul, he has a need for order and structure” flips the decision towards librarian for most people. If you have chosen A as the answer then it is wrong but the main point is to understand why it is wrong?

In similar way, any large architecture or design involves making lot of decision, though the current Lean Product Development suggests Assume variability; preserve options. It is good develop an ability to make good choices.

This session talks about cognitive bias and it's effect and how this can be addressed by using a Choice Architecture.

This session is inspired by the work done by nobel laureates Daniel Kahneman and Richard Thaler and design guru, the person behind human centred design Don Norman.

Dan Brown says the most important part of “Design Thinking” is not “Design” but “thinking”, in a similar way we can say that the most important part of “Being Agile” is to understand more about “being”than about agile.

“Being Agile”is one of the key elements of any Agile Transformation. There are many opinions, views and perspectives about – “doing” Agile vs “being” Agile. In this session on Power of Being, Ontological perspective about being Agile will be shared through practical hands on exercises. This presentation is based on the work done by Harvard Professor Michael C. Jensen and Werner Erhard on being a leader based on Ontological / Phenomenological model.

The concepts are based on Ontology, a branch of philosophy(in particular meta-physics) focusing on study and nature of ‘being’, The term is derived from Greek words, “Onto” for existence and “logia” for study, science. The session will be based on activities and learning is through participation and experience (transformative learning).

This session - Power of Being is based on Ontological/phenomological model.

In general ontology focuses on the nature being. For example, let’s consider an apple. The existence of apple can be experienced by sight, touch, smell and taste. In an apple juice, though the form is changed the existence can be experienced in the form of smell and taste. The “essence” or the being of an apple can be experienced.

In the case of living beings the concept of “being” is different, especially for human beings. Human beings have wide range of beings in which they express themselves. Normally they are expressed as emotions like “being happy”, “being sad”, “being angry”, “being enthusiastic” and so on. The being is not just the emotional state but it is much more than that. It is a combination of mental state (attitude and state of mind), emotional state (feelings and emotions), bodily state (body sensation), thoughts and thought process (logic and memory) in a given moment of time or in a given situation. This also includes mind-set (frame of reference) and world view (model of reality).

In fact, one can’t write/read about “being” then it becomes “knowing”.

From an Ontological perspective, being agile explores the “being” as the ways of being for people and teams. For an effective transition to being Agile all aspects are important.

The session will be activity based with concepts, activity, reflection and reinforcement based model.

The key element for successful agile adoption is “being” agile and not just “doing” agile. If you are using Scrum then it is not just about standups, sprints, demo and retrospectives.  Then what is this “being” agile?

Ontology is a branch of philosophy, dealing with study of the nature of being. Currently ontology based concepts are used in professional coaching and leadership development work.  (Harvard Professor Dr. Michael C. Jensen (his initiative EJI) , Prof Dave Logan of UCS author of Three Laws of Performance, have done significant research and contribution to this field).

The intention of the workshop is to give the participants a glimpse of “being” as an experience.  It is important to understand and know the difference between “doing” and “being”, since in any agile implementation “being agile” is more important than doing agile. If this distinction is not made very clear then all the agile practices will face the risk of ending up like rituals without significant outcomes.

During the sessions one key exercise is to identify the subtle differences in actions taken (doing), results obtained (having) and the experience (being). The importance that the language plays in differentiating the experience is also discussed.  After the session you will start discovering (by observation) the world of being and the world of doing and their overlap.