Software developer/manager and agile enthusiast
One interesting thing I've come across is related to unit testing in Visual Studio 2013. When you have a unit test for an async void method, the Test Explorer panel does not seem to pick this up, as below:
The solution is to modify the unit test to return a Task instead of a void. The Test Explorer should pick this up after re-build:
Essentially the difficulty of retrieving test results from a "fire and forget" method is the reason why the Visual Studio test framework chooses to ignore async void unit tests.
If you want to read more, there is an interesting article about this on MSDN magazine.
This post will describe the next steps to rolling out the use of agile to other projects, engaging the entire company in the process, and the important step of putting the customer at the heart of it all.
The previous post talked about using commonly agreed estimations to better plan the team’s work; this post will explain how you can start to engage the wider business by making progress through the work more visible.
Following on from the previous post about taking the first steps into using agile methods, this post will cover how you can progress to making better estimates for your project as a team.
In any business, changing deeply ingrained working practices can be a real challenge. As a developer you may want to employ agile working practices but meet resistance from other developers or managers in your company.