Month: July 2018
This article was originally written as a learning tool in April of 2018 during my studies of OrgMindset, I/O psychology, Human Factors, and working with Alex Yakyma on the OrgMindset body of knowledge. The article isn’t technically in a finished state since I write and learn iteratively and incrementally (so, look for updates in the future). The concepts presented here are based on empirical observations and so I wouldn’t consider this a scholarly article.
I decided to publish the article now to thank, recognize, and honor the significant and amazing contributions of Alex Yakyma. He has pushed everyone he interacts with forward in our learning in the change management and organizational transformation space. Alex is a creative and passionate, deep thinker who is a blessing to the world.
I have personally learned and grown professionally as an OrgMindset Enterprise Coach under Alex’s tutelage over the past few years. My hope is to share some of what I learned to enhance your continuous learning journey. I also reserve a hope that one day Alex will continue to develop and mine the gold and diamonds that are the OrgMindset body of knowledge. So, please share this article widely. 🙂
Adventures in slicing features.
Teams need to learn the artful skill of slicing features into stories a related to their business context and domain purpose. A typical anti-pattern is for teams to waterfall their iterations, as described in the next two scenarios.
The first iteration we will gather all the requirements, the second iteration we will design, the third and fourth iterations we will build, and the fifth iteration we will test…and so on…
Another derivation of this anti-pattern is to order up another form of phony business agility and/or Scrum.
In this iteration we will pull “requirements gathering” stories first. When those are all finished, we will pull the “design stories”, and then “build” stories…
The next common anti-pattern related to intra-waterfall is for dev team members to pull stories and work on them independently. This is a siloing ant-pattern, indicating the team is not cross-functional and is simply a collection of silos and individual waterfalls. Read the rest of this entry »