Interesting piece on how continuous — or at least frequent — delivery of releases is good for employee satisfaction and engagement. Some customers for certain applications may need to be retrained to deal w/ frequent releases, but SaaS models have eased that learning curve.
Think back to the last time you released to your customers. There was probably a brief feeling of satisfaction, hopefully a validation from the customer that you delivered what they wanted, and your team learned a thing or two about how effective they are at deploying and testing the changes that were delivered with the release. Soon afterwards, the team gets to start all over again and these lessons are forgotten.
If you think about a long term relationship, when two people haven’t talked for a while they can get nervous. “Does he still remember what I said about what we were going to do?”. “I wonder if they still feel the same way about me?”. This phenomenon is also present in product development, and the longer your team goes before releasing, the bigger impact these psychological (and measurable) effects have on the profitability of your business goals.
Keeping delivery staff satisfied
When a change…
View original post 980 more words
Filed under: PMO |