Monday, 16 September 2013

Model View Controler

MVC is the pattern in which Software is build in component architecture. The user representation is separated such that programming and expand ability of the architecture is feasible.

understanding of the MVC is simple, 

  • Let us have a DATA as separate Component( Model )
  • View in separate component                        (View)
        View in the sense what the different types of views available for the data(Chart,Screens,Pic, Analytics etc)
  • Controller controls the flow of data between the data, that means  the actual business logic is written in the component.
   Controller component can be created in a such a way to allow N number of customization for the user.

This MVC pattern is widely used in web component and application development.

Tuesday, 6 November 2012

Estimation Techniques Part 4 - Relative estimates with planning poker

Relative estimates - This suits well for iterative software development projects.  Relative estimates with planning poker is most famous way among this kind of estimation.

Here is the following steps to do relative estimates though planning poker.

 -  We need to give some points to user story/functional points based on the complexity. The points are based on relative numbers by comparing the user stories complexity based on our previous experience.

These relative points are arrived from input from team by using planner poker technique. This is similar to Delphi technique, here individual member is asked to give relative points with out knowing what other member is quoting. Then the numbers will be shown to all and based on that discussion, once again team will be asked to give points again. This process can be repeated till we arrive at an agreement.

We can use planning poker cards to arrive the numbers.  These numbers are similar to Fibonacci serious 0,1/2,1,2,3,5,8,13,20,40,100.  The idea of these points to have some division of numbers from zero to 100 with consistence intervals between such that we can give good relative points with sufficient variation.

User Stories from product Back log
Relative Points
User Story A
User Story B
User Story C
User Story D
User Story E
User Story F
User Story G
User Story H



After points are arrived a consolidated estimation can be arrived based on what is the estimation for single point and number of iteration can be arrived based on this rough estimation.

And before each iteration each team will be taking different user story based on product managers ordering. A detail estimation of user story will be asked from the team, since factors like team is different, there might some unknown the new teams might come across needs to considered.

Now it comes a concept called velocity, velocity means if team A choices user story with total counts of 20 points, then velocity of the team is 20. velocity might vary based on the team experience and knowledge level and situation. Ideally the velocity will be consistence after the team completed few iteration.

With out using cards we can use sites like to get planning poker estimates.

Saturday, 8 September 2012

Estimation techniques - Part 3

In spite of what every the techniques we are using work break down (WBS) is an important aspect we need to do before estimation.

One other technique most frequently used in functional point estimates, which is done based on the functional points from requirement document. There is always conflict of opinion that this technique work for what every be the underlying technology used.

I feel functional point estimates gives a rough estimates before getting into detail, to get closer to estimates we need to re estimate again when the technology is decided.

Friday, 17 August 2012

Estimation techniques - Part 2

I would say Delphi is an extension of expert judgement, in Delphi moderator will be getting anonymous inputs from  more than one expert.

Following are the steps followed in wideband Delphi process, difference from this method to Delphi is it has more integration for experts with each other

  • Coordinator presents each expert with a specification and an estimation form.
  • Coordinator calls a group meeting in which the experts discuss estimation issues with the coordinator and each other.
  • Experts fill out forms anonymously.
  • Coordinator prepares and distributes a summary of the estimates
  • Coordinator calls a group meeting, specifically focusing on having the experts discuss points where their estimates vary widely
  • Experts fill out forms, again anonymously, and steps 4 to 6 are iterated for as many rounds as appropriate.

Thursday, 16 August 2012

Estimation techniques - Part 1

Estimation technique , a discussion and analysis will be never ending. There is always some thing to learn on this.

We cannot have a specific technique for all the industry at all moment of time, estimation technique varies industry to industry and on specific industry time to time.One technique which can be used any time and any industry is expert judgement.   We can always trust estimation given by an expert.