Agile

Every software project includes a set of architecture decisions defining boundaries and constraints for further design and implementation. It’s important to document those decisions somehow or else a development team might not know which decisions where made and with which assumptions. Or they know the decision but are missing the context and the consequences and therefore decisions are blindly accepted or blindly changed. In the following short tutorial I will show how to structure architecture decisions in so called Architecture Decision Records and how to manage them with a simple tool named ADR-Tools. ...

Recently after a long sprint planning meeting I had the pleasure to spend some time writing down the results of the team’s task breakdown in JIRA. In our process, each user story is documented as a JIRA issue and each task from the breakdown is saved as a subtask for the parent issue. Because I am too lazy in this situation I wrote the following plugin that allowed me to quickly create multiple subtasks for a selected JIRA issue. ...

Behaviour Driven Development is the keyword when we’re talking about test scenarios written in an ubiquitous language, strong interaction with stakeholders, product owners or testers and well described, common understandable test scenarios. The popular JBehave framework is our tool of choice here and allows us to decouple our test stories from the test classes, offers an integration for web tests using Selenium and finally there’s a helpful Maven plugin for JBehave, too. ...