RISE DEV TEAM UPDATE - JAN 24, 2016And it's time for the promised update. The dev team has begun to translate the
completed Rise 2.0 architecture into user stories. This process is ongoing.
Justin and Richard are writing the user stories and Nathan is working on turning
these into code.
What exactly is a user story?
User stories are part of an approach that helps shift the focus from writing about
requirements to talking about them. All user stories include a written sentence or
two and, more importantly, a series of conversations about the desired functionality.
User stories are short, simple descriptions of a feature told from the perspective of the
person who desires the new capability, usually a user or customer of the system.
They typically follow a simple template:
As a
To give an example, here is an actual user story for Rise 2.0:
As a node i should be able to view the current blocks forging list and the prior
forging delegates.
Acceptance Requirements: Must see the function that will gather this information from
the network config collection and collect into an object or array for viewing.
The Rise Dev Team pushes each user story to Github so the community can look over their
shoulders and follow exactly what is being worked on.
There are currently 49 user stories to be viewed right here:
https://github.com/RiseVision/rise-core/issues
