OMS Consulting Partners, LLC

In the news recently, JIRA maker Atlassian announced they will no longer be tolerant, nor reward 'brilliant jerks' - those who may be hyper-talented while disregarding or even harming good team dynamics, you can read more about that here: https://www.news.com.au/finance/work/at-work/atlassian-ditches-brilliant-jerks-in-performance-review-overhaul/news-story/82a5e2abba1939f51d68ae81db8f05bd Further, research at Carnegie Mellon shows that a group of team players will always out perform a group if high achieving individuals: https://www.bbc.com/worklife/article/20190807-the-science-of-creating-a-dream-team This also parallels the ideal that "heroism" in Agile is an Anti-pattern.  What do you think?

https://www.lean.org/LeanPost/Posting.cfm?LeanPostId=1068 A few excerpts: When you think about the systems you need in place for your organization to move forward, consider Gall’s Law: “A complex system that works most likely evolved from a simple system that worked. A complex system designed that way from scratch can never be made to work. You must start over with a simple working system.” ******** Several years ago I met someone who suggested to me that leaders who create joyful environments are invariably systems thinkers. This is juxtaposed with those who try to create hero-based cultures that are laden with personality-based antics rather than simple, measurable systems. ********* This happens all the time in the software industry. We are littered with the A-player myth mentality. If quality sucks, the team let us down. It couldn’t possibly be that we didn’t accurately predict how much work there was before we set the impossible schedule. If the team misses a ...

https://www.linkedin.com/pulse/i-like-working-professionals-jason-hornberger-mba Excerpt: The best way to describe any job, which is worth paying money to other people to do, is taking something that is complicated and making it seem easy.  If I would have had the skill to build my own house, I probably would not have paid someone else to do it. If I could cook incredible food and do it in a short time time frame without having to clean it up, I probably would not go out to restaurants. There are lots of examples, but the essence of any service, is taking a task that is complicated or hard or time consuming, and making it look easy. That is why it is worth paying someone else to do it.

More amazing stuff from Henrik Kniberg... Co-author of Lean Mindset and creator of "Product Owner in a Nutshell". https://www.youtube.com/watch?v=fj5y-6AoYfM

Agile Peeps! Help support this AMAZING new book being written by Geoff Watts... There are lots of resources on Product Owners and Scrum Masters, but the actual Team is under represented, until now! https://lnkd.in/gf3BbU2 hashtag # geoffwatts hashtag # newbook hashtag # agile hashtag # support hashtag # help

Guest post by Dan Greenberg Are you scrambling to get ready for your big demo? Ask yourself these three questions: Are you about to "present" your product to a big group of people, some of whom are really important bigwigs that you want to impress? Are you nervous? Have you rehearsed? If you answered yes to any of the above, you and your organization have got a problem. The first question I'd ask is - who told us we had to hold this ceremony? Certainly not the  Scrum Guide , where a CTRL-F (or command-F for you mac users) of "demo" only turns up one result, a small bullet point (one of 8) underneath the heading of a ceremony that is actually called a "Sprint Review", where it reads that the development team "demon strates  the work that has been done and answers any questions about the product increment." How did we decide that one bullet point out of eight was now the title and purpose of the entire ceremony, especially when th...

Can someone help me name this Agile-Anti Pattern? "We keep hearing the same problems mentioned over and over in retrospectives. So they are a waste of time, let's stop having retrospectives (or at least limit them to 15 minutes)."