Archive

Archive for the ‘Project Management’ Category

What are the best practices for Java development team?

March 18, 2011 2 comments

At individual level
In Eclipse IDE use following files and share with team to maintain consistency.

PMD-rules-eclipse.xml
Eclipse-Clean-Config.xml
Eclipse-Code-Formatter.xml
Eclipse-Code-Template.xml
Eclipse-Import-Order.importorder

TestNG Test Cases
Emma plug in to check code coverage
Tie the memory and performance numbers to test cases

At team level
What happens in Hudson?
Configure following in Hudson, so that it is easy to check after each build.

Code Coverage Report
Open Tasks Report
PMD Report
Surefire Test Report

At organizational level
How to compare different projects / modules in organization?
Use SONAR and use maven plug in to push the data to Sonar server.

Code Coverage
Comments
Complexity
Lines of Code
PMD
Test Success

References:
http://java.net/projects/hudson/
http://www.sonarsource.org/
http://pmd.sourceforge.net/
http://emma.sourceforge.net/

Project Management: Fire the Tailor and save money

July 1, 2009 5 comments

Director: Director wants a shirt with two long sleeves and pocket to keep change. It should fit to all characters based on situation.

Producer: I am having only 100$ budget.

Company: Company told that it should follow ISO standards.

Production manager: Asked tailor to prepare plan and submit to stylist.

Stylist: Stylist told that, they have good idea how the shirt looks like. Also told they have standards for all shirts which are going to used by different parties based on time to time. They don’t have budget constraints and according to them final shirt can cost 300$ to get that shirt in desired fashion.

Producer: I have only 100$ budget but if we can do all as told by stylist with in that budget that will be great.

Stylist: Yes we can do it. It is easy to do. We already did this with prototype.
(In reality the prototype is not nearer to real one which needs to be produced.)

Production manager: Guys it is difficult to achieve. Let us start with Plan 1. Later we can add Plan 2 and Plan 3.

Tailor: Hello…here is the shirt as per Plan 1.

Stylist: Without my Plan 2 and Plan 3, it is not the shirt we want you guys to use.

Production manager: I will check with other producers to sponsor this shirt, So that they can also use this for their film. Asked Tailors to take the shirt through plan 2 and plan 3.

(There are three separate tailors who are specialized in stitching according to different plans 1, 2 and 3.)
Tailor: Hello…here is the final shirt which implemented Plan 1, Plan 2 and Plan 3.

Production manager: Hmm…It looks good…we got it what we need.

Stylist: Hmm…it looks great as we thought.

Producer 1 and Producer 2: Shirt looks great, you guys eat 400$ to produce this. This is too much and we are not happy. Still it is missing one more pocket. (This is not part of initial requirement.)

Question: Due to whose fault shirt rate went from 100$ to 400$?

Problems identified:
1. Prototype is not nearer to real one.
2. Stylists falsely convenience management that they can get shirt out with 100$. (If they tell upfront 300$ required, management wont agree.)
3. Instead of putting all plans together, executing three plans in three different time frames needs lot of rework hence hiked the final price.

Politics:
1. Director wants to save his face. So called for a meeting and asked production manager to identify the cost eaters. Production Manager opened his excel sheet and found that Tailors took too much time to stitch. (Everybody forgotten that they are directed to do so.). Management wants to manage themselves for upcoming projects quickly. They kicked the Tailors out and hired new Tailors who can stitch faster than their thoughts.

Poor Tailor back on road with his Scissors and Tape to find his next assignment.

-o-

Follow

Get every new post delivered to your Inbox.