We were building a prototype system to demonstrate the capabilities of a technical standard and the data that it contained. Our main stakeholders, both relatively non-technical knew the type of audience the prototype was intended to influence and making a technical standard come to life with an interactive prototype was our remit.

Agile teams are usually cross functional, which means that they have people with different competencies like developers and testers. Collaboration between the team members helps to make teams successful. Let’s take a look at what scrum masters can do to help testers and developers to work together in agile teams, and improve collaboration

With real-world samples in a variety of languages, this session will share practical, hands-on coding tips and tricks to help you turn the vision of loosely-coupled, simple components woven together with events into real code in your applications.

The phrase "agile development" has become common fare within the development community. As companies sought out new ways to innovate and optimize from within, Agile provided a new approach towards achieving productive results. Most developers have exposure to Agile in one form or another. Some companies have chosen to jump in while others have adopted select concepts. In either case, the Agile and Lean methodologies have produced frameworks such as Scrum and Kanban which have been well received. Although this might run the risk of over-simplification, Agile focuses on short cycles, fast results, and continued course corrections. After adopting this new mindset, an inevitable question arises. What do we do about technical debt? How does it fit within Agile? Does Agile eliminate or encourage technical debt?

In my last post I described the fluent calculator kata which we came up with for our coding dojo. When we started implementing the kata we decided to modify the initial set of ”requirements” slightly in order to make it a bit more complex. Here is the changed requirement: The calculator should never throw exception changed to When an overflow occurs the calculator should throw an InvalidOperationException with an inner ArithmeticException. I’ll show you what design and tests we came up with.

There are lots of good ideas and practices in Agile development, ideas that really work. But there are several common best practices that you don't need to follow - if you don't do them, nothing bad will happen and your project will still succeed. And there are a couple of them that you're better off not following at all.