June 2011
6 posts
4 tags
Jun 27th
2 notes
6 tags
Minimize requirements, maximize result
This document is a sequel to the article on our definition of ready. This is not an attempt to show the perfect requirements nor an instruction on writing requirements. This is merely an article showing how we’re trying to achieve maximum results with minimal requirements. I strongly believe requirements do not serve any purpose other than a means to communicate with developers and clients. I...
Jun 24th
14 notes
3 tags
Using a Definition of Ready
Using scrum when developing software means you want to create working software in short iterations called sprints. By doing so it becomes easier to involve customers and minimizing the time to market for the most valuable features. In order to guarantee quality during these short iterations most teams work with one or more Definition(s) of Done (DoD). The DoD makes it clear to the development...
Jun 17th
2 notes
3 tags
Jun 10th
1 note
4 tags
Jun 8th
1 note
3 tags
4 reasons to give agility a try
I recently visited a client of ours who started working with our e-learning platform. With a dedication seldom seen, they started summing up all the goals they wanted to achieve and asked me how the software could support this. I must point out this was a company with thousands of employees and probably hundreds of training programs. Somewhat stunned my reply was “..and you want to achieve all...
Jun 6th
1 note