Defining requirements of sample_project
Before beginning any work, it is good practice to go through a planning process in order to determine requirements and develop an understanding of what needs to be done. User stories are an excellent tool that are traditionally used to capture feature expectations in software projects for end users. Additionally, they work very well to define process expectations from the perspective of the developer. The basic format of a user story is as follows: as a <user role>, I want <feature> so that <purpose>. So, for instance, we might say: as a developer, I want automated JS linting so that code quality can be maintained. Each user story is that simple.
An overview of user stories
There may be a hierarchy of user stories that will begin with a master slide, (Presentation slides work very well for user stories.) as follows:
Automated build user stories:
As a developer, I want automated builds to automate repetitive tasks
As a developer, I want...
