First and foremost, the biggest change in 2013 is that I will be responsible for and managing the development team. To help the team with the challenges we will face in 2013 I will need to stay hand on too, so that should make time management critical just to make sure I can personally fit it all in. This will probably be the biggest challenge I have faced in the last few years and something . . .
2012 has been a full-on year with lots of change. I started the year in my previous role, preparing for a transition into a newly created role of “Solution Architect”; moving away from both day to day coding and purely concentrating on .NET applications/systems. It sounded a really interesting challenge but another opportunity presented itself working for my current company in another newly created role of “Technical Team Lead”. It was a hands-on development role, . . .
Not sure that this post really needs anything more than the title. If you are upgrading a Silverlight project from VS2008 or VS2010 be aware that VS2012 only supports versions 4 & 5 of Silverlight. If you need to update the solution/projects to use them in VS2012 I’d recommend upgrading to at least Silverlight 4 first in your existing Visual Studio and then once it’s working upgrade the solution/projects to VS2012 so you’re only tackling . . .
We’ve recently upgraded to Visual Studio 2012 from VS2008 and switched over to using NuGet rather than direct project references for our third party tools. Everything worked as planned until we checked the solution into source control and the personal build for TeamCity kicked off. Almost straight away the build fell over with the following error message: D:TeamCitybuildAgentworke6ae794aab32547b.nugetnuget.targets(102, 9): error MSB4067: The element beneath element is unrecognized. Project BJ.Core.sln failed. Our projects were still targeting . . .
I ran into an interesting problem today when upgrading a visual studio 2008 project to visual studio 2012, whilst trying to leave the targeted framework to .NET 3.5. Each time I tried to open the solution all my test projects automatically upgraded to .NET 4.0 regardless of what I did. It was impossible to downgrade the project using either the project property page or manually editing the project file. I’d make the change and then . . .
I’m now in my second role in which I’ve had the chance to introduce agile working practices to the team. In both roles, the projects and applications developed under scrum have been successfully shipped and accepted by the business. The success of the deliveries has been measured by: Functionality: The early visibility the business gained through the end of sprint demonstrations made sure that all the functionality the team developed stayed on track and provided . . .
What do task hours add to the overall process in scrum? This was a question that has arisen from all team members in both instances that I’ve helped teams switch over to scrum. The benefits of artefacts like the comparative story point estimation, the 2-week sprints, stand-ups and the end of sprint demo have been self-evident to the team, but as one I think every team member has expressed dismay when it comes to task . . .