Every business depends on reliable and responsive applications and with the rise of digitalisation user experience will become more important than ever before. Treating performance as an afterthought will directly have an impact on your financial revenue. Therefore, I highly recommend closing blind spots in your performance engineering approach.

Obviously, it’s not possible to reach a mature performance engineering level overnight, but you should be aware that there are eventually gaps which hold you back from achieving excellent user experience. I’ll give you now three simple steps which help you to identify the maturity level of your performance engineering activities.

Step 1 – Assessment matrix

Answer the questionnaire and understand how well you’ve implemented performance considerations in your development chain.

  • Acknowledge questions with Y (yes) if you follow this approach
  • Acknowledge questions with N (no) if you don’t have this activity in place

You can use this sample assessment matrix. I’ve answered the inquiries for a sample firm and will use their results in the two steps below.

Step 2 – Your Firm’s high water mark

Extract your score for all practices and create a spider chart because this will give you a better understanding of eventually missed opportunities. The diagram below contains the high water mark of our sample firm. Obviously, they have weak areas in their test and operate domain.

pemmhighwatmark

Step 3 – Your Firms maturity level

Finally, calculate the average of your high water mark for each domain to get the corresponding performance engineering maturity level.

PEMMMAtLevel.png

The chart above outlines that

  • our sample firms focus is on design for performance because they reached a very mature level in their build domain.
  • they have weak areas in test and operate domains which will most likely result in reduced user experience, reactivity, and missed opportunities.

Once you’ve identified the blind spots in your development process you can create a remediation plan. As already mentioned in my earlier posts on this topic, the most companies operate on level 2.

A higher maturity level will reduce the stress related to firefighting and eliminate war rooms. Finally, due to early failure identification, you will save money, hold your timelines and improve users experience.

Advertisements

Posted by JM

Resourceful, solution-focused and intuitive reliability engineer with over 15 years of demonstrated success in architecting, developing and maintaining effective testing and monitoring solutions. Offers a wealth of knowledge and experience surrounding modern application architecture and development of best practices.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s