0.2.0 (Summer 2019)

Thank you to everyone who contributed PRs, issues, reviews and moral support!

For Managers: how to migrate to this release

Ensure you've upgraded to the v2 Heatmap. Then follow this migration workflow.

Major changes in this release

For all the details, look over PRs in this release or the commit history: 0.1.1...0.2.0

• Usability

  • Improved descriptions of Impact and Frequency (#20, #29, #36 thank you @rnandi and @hiremaga)
  • Markdown tables have been formatted for better readability (#41 fixed #9, thanks @sunjayBhatia for raising that)

• Maintainability

  • Skills are now represented in yaml (#23) and migrations of the skills are captured as git diffs (#25). This means we can automatically generate the Markdown files (#16) and we can update Feedback Forms and Sheets based on the git diff by using a Google Sheets Add-on. (@rnandi and @rosenhouse with valuable design insight from @hiremaga and @dsboulder) Addresses #11 and #28.
  • We have a Contribution guide for this repo. Please follow it to help us make it better!

• Content

  • Breaking! (old response data will be archived, not migrated)

    • Improved definition of Domain Expertise skill describing other teams' use (#45 and #46, thanks @benmoss and @utako for raising the original issue #8)
    • Improved wording in Technical Execution for "onboarding pairs" (#47 as fix for #31, thanks @ctaymor for raising that)

  • New / Updates (new items / existing data will be migrated)

    • New skill arc in Collaboration based on leaving space for others (#35, thanks @ctaymor!)
    • New skill arc in Project Leadership for cutting scope (#38, @rosenhouse with valuable edits from @rnandi and @totherme)
    • Retitled and reworded the Domain Expertise area to cover domains beyond just CF (#43 as fix for #24)
    • Clarified scope of "identifying problems" skill in Engineering Process (#42, thanks @mrosecrance!)
    • Clarified "various factors" relevant to Technical Decision-Making (#44, thanks @utako for the original issue #5)
    • Clarified scope of "basic input" in Technical Execution (#30, thanks @ctaymor!)

0.1.1

Same semantic content as 0.1.0 with two changes:

• includes structured (yaml) definitions of areas and skills useful for automation.
• some small tweaks to grammar, spelling, etc in those definitions, so that it better represents the content of feedback forms and sheets that are "in the wild."

Initial release (Summer 2018)

Content used in Feedback Forms in the Summer 2018.