At kañooh we work with stories and epics. A story is a specific requirement needed to improve the system. An epic is a collection of stories.
In an epic, stories are brought together (see also the dependency graph image below) This schema helps to determine the correct ratios and order in which the stories are developed so that they get together in an epic.
The kañooh developers develop several stories that together form an epic. This happens in several steps:
- Developer 1 writes code for a story and tests that functionally with both simplest tests and Selenium tests. An upgrade path is also written (from the previous release to the future). In addition, the developer verifies that all coding standards were followed.
- Developer 2 overflows the story and does a Quality Assurance (QA) or quality analysis. If there appear to be any imperfections in the code, the story will be sent back to the first developer. If everything is ok, the ticket may be tamed.
- Our theme ensures that everything looks neat and fits inside the kañooh CMS.
- If the story is both written and tamed, it comes in UAT (User Acceptance Testing). During UAT, the work is tested for functionality and design. If everything seems to be working properly, the story ends in the epic branch.
- In the Epic branch, all finished stories come together, after which they are again subjected to UAT tests.
Support driven development
A story often occurs as a response to a customer's question or suggestion at our support service desk. Is it a question of whether a problem can be solved quickly, we'll take it straight away. So ask all your questions via firstname.lastname@example.org.
If we can make our customers happy with a small operation, we will definitely do that!