Skip to main content

Being Agile - Almost A Necessity

Neither the client, nor the consultant will be fully aware about the requirements, right from day #1. So, you need to follow an iterative process. You need to work with the client, to understand the requirements, and at times, to make him understand what he need.

A good process to follow in such cases is the Scrum process. In Scrum, you interact with the stake holders frequently, and you improve you product through various iterations. So, you can scope your requirements for various iterations, and each iteration ideally should have deliverables.
Everyone knows that you can't build Rome in a day, and any customer will understand this if you communicate in the right manner.

Scrum is an Agile process framework that allows organizations to continuously direct the project toward early delivery of real business value through the frequent and regular delivery of high quality software. In this way, requirement gaps can be caught as early as possible. Of course, I'm not going to detail the entire scrum process - but wanted to hight light that if used properly, it can really solve a lot of problems later.

As a summary, in Scrum, you have a high level product backlog, and each product backlog entry is splitted to multiple tasks. A sprint is a set of such tasks from one or more product backlogs. The set of tasks for one sprint constitutes the sprint backlog. A sprint has a defined time line and deliverables.




The main roles in Scrum are the ScrumMaster who maintains the processes and works similarly to a project manager, the Product Owner who represents the stakeholders, and the Team which includes the developers.



Read Wikipedia article about Scrum here for a fairly good introduction. http://en.wikipedia.org/wiki/Scrum_(development)


Note - If you are working in Microsoft Team System, you might consider using Scrum for team system here.  
http://scrumforteamsystem.com/en/default.aspx 


Comments

  1. Hii
    how is this Scrum is different from the incremental and prototype models that we discuss in the software engineering.Are those process not suitable for the Agile process

    ReplyDelete
  2. Scrum is surely an iterative, incremental process, but it also goes a step further and defines how the tasks are managed/organized, how the team collaborates etc.

    ReplyDelete

Post a Comment

Please keep your comments clean.

Popular posts from this blog

Creating a quick Todo listing app on Windows using IIS7, Node.js and Mongodb

As I mentioned in my last post, more and more organizations are leaning towards Web Oriented Architecture (WOA) which are highly scalable. If you were exploring cool, scalable options to build highly performing web applications, you know what Node.js is for.After following the recent post from Scott Hanselman, I was up and running quickly with Node.js. In this post, I’ll explain step by step how I’ve setup Node.js and Mongodb to create a simple Todo listing application.Setting up Node.jsThis is what I’ve done.1 – Goto http://nodejs.org/, scroll down and download node.exe for Windows, and place it in your c:\node folder2 – Goto IIS Node project in Git at https://github.com/tjanczuk/iisnode, download the correct ‘retail’ link of IIS Node zip file (I downloaded the already built retail package, otherwise you can download and build from the source).3 – Extract the zip file some where, and run the install.bat or install_iisexpress.bat depending on your IIS Version. If you don’t have IIS in…

MVVM - Binding Multiple Radio Buttons To a single Enum Property in WPF

I had a property in my View Model, of an Enum type, and wanted to bind multiple radio buttons to this.

Firstly, I wrote a simple Enum to Bool converter, like this.

public class EnumToBoolConverter : IValueConverter { #region IValueConverter Members public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { if (parameter.Equals(value)) return true; else return false; } public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { return parameter; } #endregion }

And my enumeration is like

public enum CompanyTypes { Type1Comp, Type2Comp, Type3Comp } Now, in my XAML, I provided the enumeration as the ConverterParameter, of the Converter we wrote earlier, like
<Wi…

Top 7 Coding Standards & Guideline Documents For C#/.NET Developers

Some time back, I collated a list of 7 Must Read, Free EBooks for .NET Developers, and a lot of people found it useful. So, I thought about putting together a list of Coding Standard guidelines/checklists for .NET /C# developers as well.As you may already know, it is easy to come up with a document - the key is in implementing these standards in your organization, through methods like internal trainings, Peer Reviews, Check in policies, Automated code review tools etc. You can have a look at FxCop and/or StyleCop for automating the review process to some extent, and can customize the rules based on your requirements.Anyway, here is a list of some good Coding Standard Documents. They are useful not just from a review perspective - going through these documents can definitely help you and me to iron out few hidden glitches we might have in the programming portion of our brain. So, here we go, the listing is not in any specific order.1 – IDesign C# Coding StandardsIDesign C# coding stand…