As part of IT community, analysts are working hard to keep pace with fast-changing IT industry. We always strive for excellence via getting professional certificates, attending conferences, using new techniques and tools, seeking feedback from stakeholders and simply learning from our teammates.

Having new knowledge in hand, we apply it immediately to our daily work. We can assess and improve the agreed solution, change and release the new version of requirements, and learn our lessons from any (even bad) project we took part in.

However, despite being in the environment, when we constantly get feedback and work upon it, we often fail to learn from our own mistakes. Mistakes, especially in production, are often considered as failures, and hence are often buried under a pile of new more important tasks. Time flies, and we face the same mistake again…

Why does this happen, how to avoid it, or in other words - How can we learn from our own mistakes?

IT-enabled services are challenged continuously in our fast-changing digital world. Cutting-edge systems must be accessible 24x7, seamlessly integrated and have the best UX. Software development itself has gone through an evolution from Waterfall to Scaled Agile.

What about analysis, analysts and management of analyst team?