Showing posts with label Process. Show all posts
Showing posts with label Process. Show all posts

Tuesday, 24 July 2012

Project Time Management



Whenever we work in a project , the project is generally targeted either for a market or to automate some process at the back-office which needs immediate attention.
If the project is not delivered on time not only there is a financial loss incurred it also lead to a great damage in image of the party who failed to deliver.
When we talk about commercial project we always talk about them in three 
paradigms : COST , QUALITY and TIME.

TIME is the most talked about factor whenever a project is unsuccessful , even when a project is successful most of the time we see project managers cribbing about the schedule part. Have you ever thought why most of the time we cry about schedule , why most of the time there are schedule overruns?


The reasons:
a. Its easy to measure time.
b. Time passes very quickly
c. We never take into account scope when we talk about time
d. Most of the time when scope changes , the change in schedule is overlooked.




So how can you make sure you do a proper scheduling for your project so that overruns can be avoided?
To do a proper scheduling you need to follow certain sub-process
    
Activity Definition Process
Activity Sequencing Process
Activity Duration Estimation Process
Schedule Development Process
Schedule Control Process
Following are characteristics of an activity

An activity always 
a. Consumes time
b. Requires Resources
c. Incur cost

Step 1 to schedule a project is defining the activity.
Now that we know what an activity is.
We should understand how can we define an activity.

An activity is identified by DECOMPOSITION and is related to at-least one of the rows of WBS.


WBS and Activity have a n...n relationship.

Now that we have identified the activities ,step 2 is sequencing these.To do this first understand the dependencies between the activities.
Dependencies are of three types


There are two ways in which the dependencies can be identified better:
a. Precedence Diagramming Method (PDM)
b. Activity Diagramming Method (ADM)

 Precedence Diagramming Method (PDM) : This is also called Activity on Node(AoN)

The precedence diagram method is a tool for scheduling activities in a project plan. It is a method of constructing a project schedule network diagram that uses boxes, referred to as nodes, to represent activities and connects them with arrows that show the dependencies.
Critical tasks, noncritical tasks, and slack time
Shows the relationship of the tasks to each other
Allows for what-if, worst-case, best-case and most likely scenario



Key elements include determining predecessors and defining attributes such as


An arrow diagramming method (ADM)
This  is a network diagramming technique in which activities are represented by arrows.
It is used for scheduling activities in a project plan.
The precedence relation between activities is represented by circles connecting to one or more arrows. The length of the arrow represents the duration of the relevant activity.
Sometimes a "dummy task" is added, to represent a dependency between tasks, which does not represent any activity.
This is not widely used these days.

Once , we have identified the activities and sequenced them properly, now we need to do Step 3, that is activity duration estimation.

In this step we estimate the time required for the individual activity.
We add relax time to this .
The relax time is added for contingency purpose and should not be disclosed to the team members.

Now that we have identified the activities , sequenced them appropriately and have also have came up with the estimation for duration.
Now, we need to take up Step 4 ,Scheduling the project.
Resource distribution should be done evenly.


Once the schedule is created , it should be revisited , if required it should be crunched.
Always remember ,
Adding resource may not help all the time
9 women cannot get pregnant to deliver baby in 1 month.Resources if required should be added at correct place.

Schedule can be crunched taking into consideration:
a. Leveling of resource : add less resources at start, add more during middle and slowly reduce ,use inverse for schedule.
b.Fast Tracking:Dangerous but may be used. Start modules in parallel.
c. Least incremental Cost: Schedule and resource should be redefined using the least-incremental cost approach.
d. What-if analysis and simulation 
What-if analysis is a brainstorming approach that uses broad, loosely structured questioning to:
Postulate potential upsets that may result in accidents or system performance problems
Ensure that appropriate safeguards against those problems are in place. 

We have learnt 
a. What an activity is
b. how to sequence them
c. Estimate the activities
d. Create a schedule for the project

but then,SCHEDULE SHOULD WORK IN REALITY. The scope of the project changes , the requirement changes so obviously we cannot say that the schedule won't change ever.
Schedule also goes through changes and for that purpose we have step 5 schedule control.
The first , foremost and most important thing is COMMUNICATE the changes in schedule early and clearly to the stake-holder and to do this you need to track the project closely.
Following the above process can help you be on time.

Thats all about the project time management for now.

Thursday, 19 July 2012

Test driven development

We were going through a very bad phase a little before production, when a lead came to our team and asked why so much time to implement only two pages of requirement? We were dumb stuck to hear such a question from a senior, the two paged requirement had more than 180 unit test cases attached to it, but we couldn't answer anything at that time...reason, we had no unit test to support the fact that the module was complex.

My god, I was into hell lot of problems...somehow we pushed code in production ...but it was real nightmare.


 From there on I thought...from now on I am going to do development and test hand-in-hand, piece-by-piece.
I made a note…
NO MORE RE FACTORING TO CREATE UNIT TEST CASES AFTER DEVELOPMENT.


One of my friends introduced me to the concept called TEST-DRIVEN-DEVELOPMENT (TDD)

From then, I am a better developer, a better lead and a better individual.


What is Test Driven Development?

In my terms I say, Test Driven Development is a development methodology process where the developer writes the unit test case for a particular feature before writing the code itself.

In TDD there are three rules:
Rule 1: Don't start writing a piece of code until the unit test is written and fails.
Rule 2: Don't write any more piece of code that can be tested with the unit test.
Rule 3: Re factor and test once the unit test passes.

What the rule essentially means is:
Understand the requirement; understand what feature you are going to develop, once you have understood 
Write the unit test case, run the unit test case. Till now we have not written a single line of code, so if the unit test is proper, it will fail to execute.
Now write the code to make the unit test case pass. Till now you are not bothered about the best practices to write the code...you are just writing code to make the test case pass.
Once, the unit test case passes, you can sit and refactor your code and run the unit test case again. 

This cycle of 
  • Write a test case; make it fail [RED]
  • Write the code, pass the test case. [GREEN]
  •  Refactor the code and test. [BLUE]


These are three fundamental parts of TDD. 



Why should we adopt Test Driven Development?

Ideally to avoid yourself getting into any kind of trouble like mine, you should implement TDD.

From my experience following are the advantages of TDD:
  • It helps you to better understand the functionality that you are going to develop.
  • It makes sure that all functionality is testable.
  • It helps you to make sure CODE = REQUIREMENT and you have not injected more code.
  • If you have followed the Unit test rules fairly well, then TDD will help you to make sure the code which you authored and that ran fine once , will run fine always.
  • Since the code which is written has undergone through testing it decreases the cost and time required to fix issues towards the end of development cycle.
  • The unit test cases have been written prior to writing the code, ensures that you have not compromised to make unit test pass. (This is the general thing we do when we leave unit testing after writing the code.
  • Since you have set of automated test cases written , you can add run these as a pre-build activity and enjoy.
  • This technique ensures quality and believe me it decreases schedule overruns.


General misconceptions.

When we(our team) started adopting this technique there were lot of people who were reluctant to adopt this saying it" ...adds to more time" , "cost and the project schedule will get disturbed..."."My code is very complex, it cannot be tested automatically." bla...bla...bla.

I will say all these are just excuses , implement TDD once and I am sure you are going to like it.

Is TDD good for all project types?

I won't implement TDD when:
  • I am working for an internal project
  • I have not informed client that we are going to implement TDD
  • I am not added unit testing in my project schedule
  • When the project is for a small duration
  • If automated testing will be carried
  • Even if a project has very detailed design doc available you can go with TDD , that won't cause any harm.

How can I implement Test Driven Development in .Net Projects?

We implemented TDD in our project using visual studio unit tests.You can also use NUnit for this.
Following articles give you a detailed overview using NUnit.


Friday, 29 June 2012

Pareto's 80:20






Pareto's Rule, I encountered first time in 2004 December, during my training at Mysore.

The Rule Says: 80% of effects are caused by 20% of causes.

I believe 80:20 holds good for everything: Job, Love, Life, and Marriage everything on earth runs basically on Pareto's 80:20 principle.

A glimpse at the rule:
The principle was suggested by management thinker Joseph M. Juran. It was named after the Italian economist Vilfredo Pareto, who observed that 80% of income in Italy was received by 20% of the Italian population. The assumption is that most of the results in any situation are determined by a small number of causes.

It really doesn’t matter what numbers you apply, the important thing to understand is that in your life there are certain activities you do (your 20 percent) that account for the majority (your 80 percent) of your happiness and outputs.

Love this rule, it’s interesting and you can get run a successful business just by analyzing all problems using this basic rule.

80% of business comes from 20% of customer.

80% of a manager's interruptions come from the same 20% of the people.

80% of a problem can be solved by identifying the correct 20% of the issues

80% of advertising results come from 20% of your campaign.

80% of an equipment budget comes from 20% of the items

80% of an instructor's time is taken up by 20% of the students

80% of benefit comes from the first 20% of effort

80% of customer complaints are about the same 20% of your projects, products, services.

80% of network traffic stays within the LAN while 20% needs to cross the backbone.

80% of our personal telephone calls are to 20% of the people in our address book .

80% of our shipments utilize 20% of your inventory.

80% of sales time is spent on 20% of the customers, who may not be the profitable 20%

80% of the decisions made in meetings come from 20% of the meeting time

80% of the outfits we wear come from 20% of the clothes in our closets and drawers

80% of the traffic in town travels over 20% of the roads

80% of what we produce is generated during 20% of our working hours

80% of your annual sales come from 20% of your sales force

80% of your future business comes from 20% of your customers

80% of your growth comes from 20% of your products

80% of your innovation comes from 20% of your employees or customers

80% of your profits come from 20% of your customers

80% of your staff headaches come from 20% of our employees

80% of your success comes from 20% of your efforts

80% of your website traffic comes from 20% of your pages 

Reverse all these are they are also true

20% of customers give you 80% of business. (May not be true always.)

20% of issues create 80% of problems.

20% of campaigns give 80% of advertising results.

And so on…

So, finally the rule is completely dependent


To start living 80/20 today you have only to do one thing – focus your energies on what you enjoy.