Accelerate the overall development time, ensure product owner and developers communicate efficiently,
and the team is confident about its product and its development
If you already apply Behavior Driven Development in your team, in other words, if you define the user stories with your product owner with examples in your Given When Then steps : you probably agree with the following statements :
BBD is a good way to start the discussion with your product owner. This is a contract between the product owner and dev team.
Instead of having a 2 weeks loop of feedback, you have a 2 hours loop of feedback.
BDD scenarios guide the dev in the implementation of the feature.
To have the features defined at compoent level make the refactoring at component level possible and easy.
You have now an exhaustive accurate and executable documentation.
The exhaustive accurate and executable documentation is not really accessible. The interactions with the product owner are not always easy.
Give an easy access to the exhaustive accurate and executable documentation. Write scenarios through an application shared with all members of the team
Generation of the documentation (almost done)
Write scenario through a workflow (planned)
Play / Scala on the back. Angular on the front.