Thoughts on how to define and document scope when building software products, identify various assumptions, test those, and communicate with stakeholders to bring something new and valuable to the world. And do all of that with visual notes!
Note from the editor
Thoughts on how to define and document scope when building software products, identify various assumptions, test those, and communicate with stakeholders to bring something new and valuable to the world. And do all of that with visual notes!
Ukrainian guy who writes stories, enjoys calisthenics and kyokushin, happily married, dreams about travel to South America. Lives in Northern Utah, Logan.