Framing Results

It's one thing to get results.  It's another to articulate them.   Having a way to frame results can help both for personal learning, as well as review time when you have to reflect on accomplishments.

Commitment, Results, How, Evidence, Analysis

I've found framing results by listing the commitment, the results, the how, the evidence and the analysis to be pretty effective over the years.  I'm a fan of concrete examples, so here's an example:

Architecture Reviews Results
  • MSF Agile changed their original threat modeling approach to align with our updated approach.
  • 10 DCRs submitted to product teams.
  • Security scenarios were used by STBU to focus developer security efforts.
  • Cross-product/technology guidance that addresses key customer customers.
  • Accelerated Analysis Design (AAD) Session. Held an AAD session with partners, customers and extended team to analyze and prioritize problems within the application security space, while evaluating .NET Framework 2.0.
  • Scenario Evaluations. Evaluated .NET Framework 2.0 platform, tools, and guidance in the context of application security.
  • Whiteboard Walkthroughs. Held whiteboard walkthroughs with the CLR team, ASP.NET team, MSF Agile, STBU marketing
  • Randy Miller, PM, MSF Agile. “ … we are building links into MSF to Patterns and Practice online material. Thus the activities in MSF and the patterns and practices enjoy a very complimentary relationship. The patterns and practices group continues to be very helpful and our relationship is one of very open communication. “
  • ASP.NET Team. “Your guidance cuts across a number of products and shows how to integrate them - as opposed to product group specific documents that are much more narrowly focused.” Improved confidence in Customers Ability to implement secure application improved from 4 to 7 with patterns & practices security guidance.
  • Building mental and conceptual models to frame communication was the key to effective collaboration with product teams.