Entry Guide
The following are comments gathered from previous Judging Panels after they had reviewed all entries. It may help you in deciding on what information to include in your entries.
As a whole the entries did not take into account criteria as much as the Judging Panel would have liked. Additionally, the entrants should remember that they are being judged by a panel of industry peers and so would do well to pitch the entry to the target audience. A few entries were considered “overly simplistic.”
Strong Entries:
Successfully emphasised the project’s critical business importance and its innovative approach, establishing its strategic value.
Excellently demonstrated a full spectrum of leadership and people-management traits, including mentorship, coaching, being a role model, and a dedicated focus on team well-being and continuous skill development.
Clearly evidenced overcoming specific automation challenges, with a strong commitment to best practices and a well-justified methodology that made the application stand out.
Went beyond standard practice by researching and implementing comprehensive technology to test the entire integrated system, not just the isolated backend software.
Provided a very clear and detailed description of the project methodology, stakeholder needs, and overall goals, showing deep strategic understanding.
Included all relevant metrics with clear context and a robust justification for their inclusion, effectively demonstrating project success and impact.
Weak Entries:
- Weaker applications often failed to describe challenges effectively, focusing on generic business or architectural issues instead of specific obstacles within their automation journey.
- Many submissions were weakened by not addressing all the required criteria.
- A common shortcoming was a lack of detail in the testing approach. While a diagram might list the tools used, there was limited explanation of the specific challenges faced and how automation helped to overcome them.
- Applications frequently lacked evidence of delivering on time, working within budget, or engaging stakeholders. There was also little reflection on whether the original project goals were met to demonstrate ultimate success.
- Many entries concentrated on the merits of a particular tool or methodology, rather than on the tangible project deliverables, which is less likely to result in a high score.
- Finally, applicants often included metrics but did not justify the reasoning behind their selection.