Tag: Agility

INNOVATION ROOTS Announces Taoism and Agility Webinar with Dov Tsal

Alekya N.R Leave a comment

We are pleased to announce the next webinar on “Taoism and Agility” with Dov Tsal, which will be held on June 28th 2018. Dov Tsal is a well-known personality in the Agile industry. He is a versatile Change Agent and enabler, helping companies, teams and individuals make in impact in their career.

This webinar will start sharp at 7:00-8:00 PM with an introductory session by Dov Tsal about Taoism, and continues further on the agenda of the webinar. Participants will learn about Taoism, and how was Taoism adopted as an Agile practice in ancient times. Dov Tsal will make the audience walk through the segments of the fascinating book “The Agile Tao” by Peter Merel.

The participants will get an opportunity to explore the Agile principles that are linked to Taoism philosophy which includes Self-organization, Reacting change over following a plan, Maximizing the work not done, Progressing in a sustainable space. In this webinar, you will get hold of the some fascinating points about how Taoism practices brings harmony in an organization’s progress to Agile transition.

Audience: Agile Practitioners, Project Managers, Change Managers, Consultants and Coaches

To learn more about this webinar and upcoming events, visit: www.innovationroots.com

Rule of Simplicity | Glossary

Prashant MJ Leave a comment

Definition:

Kent Beck while developing Extreme Programming (XP) came up with rules of simple design. He recommended that developers should do the simplest thing that could possibly work. Simple code means you’re travelling light – low up-front investment, and not much to slow down when things needs to change. Simplicity is being recognised as one of values in XP, where programmers are encouraged to start with simplest solution which helps them to focus on designing and coding for the needs of today instead of tomorrow.

Rule of Simplicity

  1. Pass All Tests
  2. Clear, Expressive & Consistent
  3. Duplicates No Behaviour or Configuration
  4. Minimal Methods, Classes & Modules

With these rules, we can judge whether the code developed is simple enough. What we can derive is to think about what is most important, the code should work, pass all tests. The next most important thing is that the code should be easy to understand, therefore we need to ensure that it expresses every idea  with clarity. Even though the code works, we need to consider maintainability, see to that there is no duplicate code. This minimises cost and maximise benefits over the lifetime of the software.

Further Reading:

Book: Extreme Programming Explained: Embrace Change by Kent Beck
Book: Understanding the 4 Rules of Simple Design by Corey Haines
Book: Understanding Software by Max Kanat-Alexander
https://en.wikipedia.org/wiki/Extreme_programming
http://wiki.c2.com/?XpSimplicityRules
https://martinfowler.com/bliki/BeckDesignRules.html