Aggregated feedback for several pages

[joemoore]

At my request a Tanzu Labs employee reviewed several pages and provided feedback.

---

https://tanzu.vmware.com/developer/learningpaths/application-development-how-we-work/principles/

• A link to EPIC2 page would be good to add, when it’s mentioned in the bottom of the page:

  https://news.vmware.com/company/vmwares-culture-built-epic2-values

• The use of icons are eye-catching but (to me) distracting, as other tracks do not use them.

• Overall, the contents in this Learning Path is based on the traditional Pivotal Labs ways. I wonder if there is anyway to highlight distinctive patterns employed by Platform Service team, which I believe is now part of Labs (e.g. https://tanzu.vmware.com/platform-development )

https://tanzu.vmware.com/developer/learningpaths/application-development-how-we-work/work-life-balance/

• A very short page. Perhaps, we can add a nice picture of smiling, diverse Labs folks, hanging out.

https://tanzu.vmware.com/developer/learningpaths/application-development/balanced-teams/

• The video is super informative and well-putgether. Given the current temperature in the society, however, it may be good to have participants from Under-Representative Minorities (e.g. African American)
• One thing to highlight moreof for benefits of Balanced Team is that it enables Empathy for each discipline but moreover for users. The most common compliment I heard from my client engineers is that they become much more empathetic to users, as they were able to participate in user testing as part of working in a balanced team.

https://tanzu.vmware.com/developer/learningpaths/application-development-rhythm/foundations/

• May need to add a link to Development Flow article (https://tanzu.vmware.com/developer/learningpaths/application-development-rhythm/dev-flow/) for easy access:

  It’s also a good idea to become proficient in how each of the tools and technologies work, as this is the best way to minimize friction in the Modern Apps Practitioner Workflow.

https://tanzu.vmware.com/developer/learningpaths/application-development-rhythm/dev-flow/

• Add a link to Mikado Method? http://mikadomethod.info/n or to the build block part 2 page, where it’s discussed
• For the Backlog section, to help educate readers on the user story and backlog in depth, a link to the following page would be beneficial: https://tanzu.vmware.com/developer/learningpaths/application-development/prioritizing-outcomes/#stories

https://tanzu.vmware.com/developer/learningpaths/application-development-rhythm/dev-building-blocks-1/

• With a pull based model, *the- [ ] you pull the latest changes into a local development environment and verify integration locally before merging the changes back to a shared repository
• The link leads to a missing Wiki content: “The Pomodoro Technique is a good tool to help you timebox.”
• Under the “Accelerators” section, it may be good to add a blurb and link to Tanzu Application Platfrom’s app accelerator: https://docs.vmware.com/en/Application-Accelerator-for-VMware-Tanzu/index.html
• In the “Developer Tools” section, we may want to introduce Pivotal Workstation Setup github project, as an example of a good dev setup with short cuts, etc
• [ ]

https://tanzu.vmware.com/developer/learningpaths/application-development/team-rhythm/

• A great reminder of Office/cross-team Standup…. Which we don’t really practice any more (at least in the South)
• Love Tips, as it gives out the feeling we are the experts who like to share.We should have more of it on other pages

https://tanzu.vmware.com/developer/learningpaths/application-development/product-validation/

• Noticed a new way of using the bubble. Is this supposed to be an example? Perhaps, we can standardize use of icons… The bulb has been used for Tips on other pages.

https://tanzu.vmware.com/developer/learningpaths/application-development/pair-programming/

• Highlighting that pairing is not just for developers may be good, as cross-displine pairing has been tremendously beneficial (e.g. pairing with designers to better understand user experience, etc)

https://tanzu.vmware.com/developer/learningpaths/anchor-playbook/

• Overall, I love the anchor playbook. It’s a must read for the first time anchors.
• I wonder what the benefits for coining the word “anchortype”. I think it somehow forces me to choose a type, where, in fact, I feel an anchor on an engagement may experience being different types. It would be good to point that out, explicitly.

[joemoore]

Merged the easy ones.