# Lessons Learned From The Entelect Way

DevFeed: [Lessons Learned From The Entelect Way](<https://devfeed.tech/articles/lessons-learned-from-the-entelect-way-22304.md>)

Original publisher: [Read original article](<https://www.thecodedself.com/Lessons-Learned-From-The-Entelect-Way/>)

Author: Keegan Rush

Published: 2017-05-08T00:00:00Z

Content type: opinion

Language: en

Sources: [The Coded Self](<https://devfeed.tech/sources/the-coded-self.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

## AI overview

A software engineer reflects on lessons from an Entelect Way workshop, focusing on software delivery principles, understanding clients' underlying goals, continuous communication, resilience, and team learning.

## Source excerpt

Software engineering and coding are two very different concepts. As a software engineer, I write code on a daily basis, but the value that a good software engineer provides to a business is so much more. This is emphasised by The Entelect Way. What is The Entelect Way? I'm a software engineer at Entelect, a software engineering and solutions company based in South Africa. The Entelect Way is a set of guiding principles for software delivery that can be used to help guide your decisions, activities, and behaviour as a professional software engineer. The principles are broken down into the following areas of focus: Agile Planning and Development Software Engineering Quality Practices Individual Growth Team Engagement Relationships Value Adding Activities First Class Service Delivery The Workshop A few weeks ago, my team attended a workshop on The Entelect Way with a few teams based at other clients. We took a deeper look at each of the principles and were encouraged to find ways to apply these principles in our day to day activities. Our Findings We were asked to discuss Value Adding Activities. We chatted about each team's strengths and weaknesses around the points raised during the workshop. I realized what our team does well - and where we need some major improvement. While we didn't stay entirely on topic of Value Adding Activities, we did manage to learn a lot from each other that we then compiled into a list. Here's the best picks across our three teams: Focus on your client's 'why' You can take action on your client's what, or you can take action on their why. Try to find the why, and use that as your guide. Imagine you're fetching data from a service and displaying that to the user. If someone asks you to attempt to make the service call three times in the case of failure before displaying an error message, they're asking for the what. The why is likely to be something along the lines of "I don't want the user to visually experience errors when the server goes