Processes captured in the everyday language of the end user.
- User stories are written from a user's perspective, and describe how and why the user is using the software.
- User stories should satisfy the INVEST principles.
- For a user story to be ready for development, the team should be able to describe the technical tasks (develop, test, deploy) for the bug fixes and new features required to complete that user story.
- Just about all user stories follow this structure:
- As a <type of user>,
- I want <some goal>,
- so that <some reason>.
- User stories must be prioritized by the product owner so that highest value features are completed and delivered first.
Wednesday, February 24, 2016
Biographies of fictitious users of the future product.
- Personas are a way to visualize all the future users of an application.
- With personas and BDD, we can design user stories based around these understood roles.
- Begin with a table 3 columns wide.
- Title the columns:
- Picture & Name
- Personal Information
- Goals & Responsibilities
- Create semi-fictional personas for all possible users; considering chief officer, investor, auditor, regulator and manager in addition to the usual buyer and seller.
- Google image searching for the job title is a quick hack for believable pictures.
- Enter semi-fictional personal data to complete the personas.
Monday, February 22, 2016
- Barman is a database recovery tool.
- Install Barman with yum on the backup server.
- Verify the barman user has ssh access to the postgres user on the main server.
- Verify the postgres user has ssh access to the barman user on the backup server.
- Verify the barman user can connect to the database on the main server.
- Configure Barman with default settings, noting the incoming_wals_directory.
- Configure Barman to enable continuous WAL archiving.
- Restart the server.
- Test new backup and restore functionality.