My teammate feel not really satisfied with the ALM features on VIsual Studio 2013. It is great, but lack of simplicity for small to medium project. After using Visual Studio for almost than 15 years, I agree that ALM is a good feature, but not as for startup who still fighting with the client changes and codes horror. Of you already subscribe to visualstudio.com and feel that you still focusing on the codes or API usage. focusing on the collaboration between client and you in terms of changes control. focusing on planning schedule rather than thinking the burndown chart. If you feel like the situation above is same with your team. This article is for you, this article will show you how to minimize the usage some of redundant TFS features on small and mediim project. This practices is already done on more tha five projects that run on two till six months. We call this practice as ALM minimalist. The ALM minimalist purpose is to Empower the client and your team through multimodal communication Empower the team to focus on creating quality codes by adopting eXtreme Programming practices Empower the coach / project manager to minimize the changes and to get better revenue on a project. With the three purposes of ALM Minimalist. the practice needs several subscriptions for your team which are Office 365 subscriptions Visual Studio Online Subscriptions After you subscribe both services, we will discuss how to utilize the services for ALM activities, see you in the next post. cheers, @ridife
In a hurry?
Building in a three months or less, well you can depend on Agile method like eXtreme Programming (XP) or Scrum. In this article I will show you several things to do if you wish to use XP as your Agile method.
First of all, XP need a discipline. Forget it, if you have a team that have no spirit to work in time and always postponed their tasks. You can read the entire tasks in Meier's Blog. The entire tasks is not a must, you can use it when you are really need it. If you are a new kids on the block of XP try to buy the books below
If you need more simple way to adopt the XP. I constructs a tiny XP method called my-XP. my-XP is a mini implementation of the XP. In my-XP, we just need several artifacts which are
User story document. http://www.agilemodeling.com/artifacts/userStory.htm
Spike Solution document http://c2.com/xp/SpikeSolution.html
Deployment diagram http://msdn.microsoft.com/en-us/library/ms181902(v=VS.80).aspx
the rest of it is just well tested code. test driven model focused in creating test unit and then evaluates your code. If you are using Visual Studio 2010 ALM or others IDE like Eclipse you can get free unit test tool. several references below
How to- Create and Run a Unit Test - MSDN – Explore Desktop
How to- Create a Data-Driven Unit Test - MSDN – Explore Desktop
How to- Generate a Unit Test - MSDN – Explore Desktop, Web
How to- Create an ASP.NET Unit Test - MSDN – Explore Desktop
How to- Create a Unit Test without Source Code
Adopting scrum is just like adopting any agile method such as extreme Programming or ICONIX. However, Scrum lays out the playing field and rules for the game. the software construction is a game for Scrum. Scrum adoption has two aspects. First, Scrum is rolled out. a mentor teach a team how to play the game of product development using Scrum, the second aspect is do the SCRUM itself including your team and client. A good guide about scrum can be downloaded here
15 pages of Scrum Guide
Schwaber (2007) in his book called Enterprise and Scrum already have 1,2,3 rules to adopt Scrum.
Creating backlog, a simple user story model
Iteration activity as a heart of the Scrum
And working software that increment the functionality
The rules is done by three roles the Product Owner, the team, and the Scrum Master. All management responsibilities in a project are divided between these three roles. The Scrum Master is responsible for the Scrum process, for teaching it to everyone involved in the project, for implementing it so that it fits within an organization's culture and still delivers the expected benefits, and for ensuring that everyone follows its rules and practices. The Scrum process is simple and mostly focused how team collaborate effectively using daily plan and appropriate tools. You can learn and develop a software with fun using this method. For further knowledge I recommend you to buy and read several books below