Why When and How to use web based project management

systemwhen implementing

Agile

Data not updatedWaste of time

Agile manifesto

People & Relationship

Quality

Time

Complex process require an empirical control modelthat entails frequent feedback loops

How to use the tools to facilitate effective short

feedback cycles ?Encouraging commitment, trust and avoiding creating

waste

To do: User stories the team committed

to do

In progress: User stories the team

currently working on

Done: User stories the team completed

Task boardEach user story is being moved by the teamTo it’s relevant column

Facilitate effective team collaboration:• Team goals orientation – Focus, commitment, cooperation• Visual progress• Makes problems visible

Easy to use, easy to learn – intuitive, simplePhysical – interactive

Flexible, may be adopted for teamInexpensive

What are the principles of the physical visual board that allows it to facilitate effective team work ?

Visualize the InvisibleVisualize the work

Transparency - trustCommon languageCommitmentPositive conflict resolution

Information radiatorsPush vs. Pull

Commitment • Volunteered• Written• Public

Why use electronic project management tool ?

Distributed teams• Offshore• Nearshore• Remote teams

Scaling up

• Reports• Reuse of data • Track progress• Have history

5 Tips on how to implement electronic project management tool

Tip #1 -Start with physical whiteboard

Tip #2 –Start with the team

• Public visual board – story driven• Facilitate team’s daily meetings• Team member ownership (create, update)

Tip #3 – continue using the sticky notes

• Facilitating team discussions and decision making- planning sessions, retrospectives…

Tip #4 Management -Visualize project progress

Tip #5 -Improvement visualization

Dangers

• Becomes a form of communication• Create wastes: too much data to input and track• No– go see- detached from the people and

where the work is really done• Makes heavy process – (policies, workflows,

data)• Invisible – creates confusion• Owned by project manager\managers

Tool properties• Natively support common Agile practices

• Iteration planning• User stories • Reports: CFD, Burn down\up charts• Acceptance testing, unit testing, continuous integration• Automated builds

• Multi vendor approach \ customizable• Complete integrated development life-cycle solutions• Distributed collaboration tools

Sources• http://www.slideshare.net/choldorf/agile-tools• http://www.slideshare.net/jurgenappelo/agile-alm• http://www.slideshare.net/larrycai/agile-alm-tools-9103260• http://www.slideshare.net/manageware/complex-agile-backlog-management• http://www.slideshare.net/tasktop/scaling-agile-in-the-enterprise-agile-day-2012-

presentation• http://www.slideshare.net/Byungwook/alm-application-lifecycle-management-114

9823• http://www.slideshare.net/venj123/agile-alm-tool-comparison• http://www.slideshare.net/clemensreijnen/alm-getting-testing-done-in-a-sprint

• http://agiletools.wordpress.com/2007/11/24/task-boards-telling-a-compelling-agile-story/

• http://www.eylean.com/blog/