This week we look at replacing the agile manifesto, better design critiques and better software testing.
Enabling the Team
Exact Instructions vs. Social Competence by Michael Bolton
Often we blame mistakes on poor requirements or a lack of documentation. But perfect documentation is impossible - collaboration is key.
Better Coordination, Or Better Software? by Jessica Kerr
Making coordination easier can hurt teams. It is better to define clear boundaries and reduce coordination.
Product Vision
Agile Manifesto Is Long Gone! We Need A Product Manifesto! by David Pereira
The agile manifesto was focused on software - we need a product manifesto which is focused on outcomes.
Product Vision FAQs by Marty Cagan
Answers to the common questions about developing a product vision.
Continuous Research
Dissecting User Experience by Harshit Daga
The 4 cornerstone of UX (defined in 2008) are still valid. Harshit shares examples of what brands best follow these rules.
UX Researchers And Product Managers: A Guide To Effective Collaboration by Hossein Raspberry
Best practices on ensuring a successful collaboration between UX Researchers & Product Managers.
Ideate & Design
All You Need Is 5 Fonts by Matej Latin
Matej notes that designers only need 5 base fonts to create great designs. Read through what fonts he uses & what base fonts you should be using.
The W.H.Y. Method for Better Design Critiques by Ava DeVoe
Using the W.H.Y. Method during her design critiques has given Ava the structure for a successful & effective critique where each member is valued & heard.
Architect & Build
We Need To Talk About Testing by Dan Terhorst-North
The purpose of testing is to increase confidence for stakeholders through evidence. TDD helps design better code but it doesn't replace testing.
Six Common Testing Pitfalls And How To Solve Them by Ramona Schwering
Flaky tests, slow test runs, painful maintenance. Automation can save time if you avoid some of these traps.
