When developing a new product, like a house or an app, we could use many different ways to track issues and manage the project. One way is to look at a software development process. For example, Coorie Home is progressing into the Design (Feature) phase:

Idea > Design (Feature) > Code > Test > Release > Feedback

The Acceptance Criteria, or the formal set of rules for the phase, for the Design phase, are what we established on our Coorie page: Sustainable & cozy prefabricated straw bale home. The Coorie Homes will be built with the Coorie ethos to connect the family to nature in sustainable coziness.

Note that we are not in the Code phase as the Code phase would be actually building the product.

Let us know how you think about these Acceptance Criteria. Does it resonate with you? What would be an alternative? While we might be done with the Idea phase, the whole process repeats itself at all stages of the product release by using feedback loops. One such feedback loop in Software development is accomplished by writing a Manual Test Cases scenario:

Case Name: Construction Class

Setup: Enroll in 4-week course to get OSHA 10 certificate

Steps #1 Name: Complete course

Step #1 Expected Outcome: Show up on time 4x per week, from 5 to 8pm for 4 weeks

Step #2 Name: Network with partner companies

Step #2 Expected Outcome: At the graduation, network with potential companies, ask about prefab construction techniques, Straw Bale techniques, and how IT departments work within the construction company.

Step #3 Name: Share Learnings

Step #3 Expected Outcome: Create a video about my experience and reflect on what I learned

Teardown: Use what I learned in the Constitution Class to improve Coorie Home.

Dear Customer,

As Coorie Home starts on the journey of creating sustainable & cozy prefabricated straw bale homes, we want to invite you to feel free in giving feedback as we share this journey. Please let us know what you think!

Regards,

Blake