Showing11 -14 of14 posts.
Having an agile mindset is part of the eMundo spirit. We have lots of agile projects, so basically everyone must know about this. Yet, sometimes, doing agile software development is harder than expected.
To get around this, we developed a game - "The Temple of Grog" - that tries to teach the contents of the agile manifesto without actually doing software development. This makes it much easier because of the domain being completely inconvenient to any single workshop participant.
On a regular basis, you may want to tag the master branch with a (beta) version that is deployed to a customer's staging system.
People not engaged in development themselves (e.g. product owners) usually have a hard time following the changes that are made available with each new version. So the easiest way to help them is to create a readable changelog from the git log.
In an iterative, continuous development process, manual tasks must be reduced to guarantee a high level of quality over time without reducing velocity. Testing the artifact is one of those tasks.
This post describes our way of calculating a coverage value by taking rspec-/watir-based tests and CARDS+ cases.