In November of this year, 2014, I gave a talk on Essence at Binghamton University to a group of Computer Science students. You can catch the highlights of Part I of the talk on YouTube. This is a great video to watch if you want to learn what is new and different about Essence, the new software engineering Object Management Group (OMG) standard intended specifically for software practitioners. If you don’t have time to watch the complete Part I– which is about 44 minutes– you can find a cross-reference at the end of the video to where in the video you can find the following 23 key topics:
- What is Essence?
- The Difference Between Scrum and Essence.
- What Does Essence Contain?
- Why Did We Create the Strange Alpha Word?
- What is Different About Essence?
- The Essence CARD Deck.
- An Example Demonstrating How Essence is NOT Waterfall.
- A Question About Essence Versus Scrum.
- How Essence Can Power Whatever Approach Your Team is Already Using.
- About the Problem We Are Trying To Solve With Essence.
- How Does a Team Use the Essence Model?
- How Essence Checklists Are Different.
- How Do Teams Apply the Essence Checklists?
- On the Importance of Knowing When You Are Done.
- A Question on How a Team Can Fall Back.
- On the Order You Address States, and Decisions on Checklists that May Not Apply.
- An Example of a Team Deciding if a Checklist is Applicable to them.
- On Activity Spaces.
- Competencies Within Essence.
- How to Figure Out if You Have a Leadership or a Management Competency Issue.
- What if a Team Can’t Meet a Checklist Item?
- Why Isn’t Risk an Alpha?
- Why is Hardware included in the Definition of the Software System Alpha?
As always, your comments and feedback are encouraged.
A new blog has just been posted about an interesting discussion recently taking place in an Essence User Guide meeting.
A new article has just been published that might be of interest to those following the work of SEMAT.
As always, comments are encouraged.
In August, 2014 (this year) I faced this challenge when speaking at the Latin American Software Engineering Symposium (LASES) in Barranquilla, Columbia. The night before the talk Dr. Carlos Zapata and I came up with an idea that not only worked, but also generated more questions than I ever imagined.
The title of my talk was: Essence: A Practitioner and Team Performance Perspective.
Take a look at this video to see how we pulled this off. Below the link to the video find a sampling of the questions I received and how you can locate them quickly in the video.
Following is a sampling of the questions I received during the talk:
- Why are there only 7 alphas in the Essence kernel?
- How long will the SEMAT community work on Essence?
- Why don’t we see practices represented on the kernel?
- What is the vision for how companies will represent their practices using Essence?
- Will there be more disciplines added to Essence?
- How is the kernel changed, and what changes are coming?
- What criteria was used in selecting Essence checklists?
- What is your vision for the future of Essence?
- How would you sell Essence to companies?
- Where are we headed with practices on top of the Essence kernel?
- What is the definition of practice from the point of view of the Essence kernel?
- How will practices be captured in the Essence framework?
If you don’t have time to watch the entire video, jump to the end of the video where you will find, along with the 12 questions above, 30 more key questions/concrete examples listed and a reference to where you can find them quickly in the video (minutes and seconds into the video).
There has recently been a lot of discussion related to quantifying the value of using SEMAT’s Essence Framework. I just posted a blog on this subject at:
I’d love to hear what you think…
A Slightly Different Way to Think About the SEMAT Vision and the Essence Framework by Paul E. McMahon
I have just posted a blog about a different way to think about the SEMAT vision and the Essence Framework.
I would love to hear what you think.