Sharing Info

Sharing Info

As Projects continuously grow in size in a dynamic country like India , attrition can not be stopped. So what do you do ? First Reduce Attrition.

And Capture as much info as possible. Capturing info is not just documentation.

• Training Sessions (peer2peer ) and otherwise
• Post Project Examination (post-mortem)
• Summary across Projects.
• Post Project Personnel Interview

These are just some tips. You will need to Innovate anyways

OffShore and outsourced Projects

OffShore and outsourced Projects

Off-Shoring Projects
Projects are offshored for many reasons such as derth of people in a given technlogy, cost , location of client and a whole lot more. For whatever reason you are outsourcing it, the key factor is successful implementation.

There are two varieties of outsourced / offshored Projects

• Self-mananged and
• Client Managed.

In Both the models start out wiht having faith.

Don't Fire people in the first week : They need to audjust to your style of doing things.

Language: People mess up when they speak. Dont watch the words. Understnd the meaning.

Adopt small mouldes .Use Xtreme Pograming or Agile techniques to get control over the tasks.

Last but not the least Have a Mentor.
To achieve success start with the best foot forward. Have Faith ! Oh yes !

Some Best Practices In XP

Some Best Practices In XP

• Let it Sync


• Mentor your Team


• Don't Force Pair Programming


• Continue to Test


• Refactor Code


• Backup your code
• Last but not the least -Innovate -Every project has it own challenges.

Roles In eXtreme Programming

Roles In eXtreme Programming

Two Main Roles
On-site customer
Developers
Supporting Roles
Team Lead (Coach)
Tracker Checks in every now and then. do you have this checked in yet?
Project Manager


The Rest Of the crew is not seen and is above the PM.

Steps In eXtreme Programming

Steps In eXtreme Programming

User stories are written.
In this phase, a 'Small Spec' is written out. It often includes the developers too.Not just the functional team.

::FACT:: There can huge advantages of not writing a whole lot in the Spec. That does not mean you miss conveyaing the requirement. This is because the reality in Project Management is that People Know what they really want only after they see half the piece.

It is a bit like shopping for the decoration items for you house. It takes a while before the customer can see what he wants. This is very true if the company /project is less than 10 years old. And the fact is there are a lot of them.

:: FACT :: Dont Jump Into Coding ! Read the User Story.

Iteration Planing Plan a small increment /changes
Helps Make Make frequent small releases.

Release planning creates the schedule.

Small releases Help Track Bugs and helps you to plan for them.

Note : Track Your Project :: But Don't Mess up the happyness of your developers! Have faith in them. ::

Note :: Plan Buffers and track Buffer Absorbtion a the Project Level. ::

Agile Project Management Vocabulary

Agile Project Management Vocabulary

Vocabulary
Customer: the person or group defining the need for the system.

Story: a feature or capability of the system that a customer values.

Estimate: the cost (usually time) to implement a story. In XP, estimates are relative; a story is estimated as costing 1 to 3 "story points."

Programmer: the person or group that estimates and implements stories.

Team: the customers, programmers, and managers who are jointly working on the system.

Release: delivery of system (usually to end users).

Exploration: part of the release cycle: when customers create stories, and programmers estimate them.

Iteration: part of the release cycle: a fixed-length time for implementation of stories. An iteration is time-boxed: if all stories can’t be completed, stories are dropped rather than the iteration extended.

Release Plan: a flexible, overall plan that tells which stories are expected in which iteration, for a whole release.

Iteration Plan: a small plan that tells which features are expected in the current iteration.