TenForce – Pragmatic Project Management

What’s in our personal TenForce:

• All our backlog items
• Full release (sprint) content
• To do lists for all engineering and support people
• Invoices are based on TenForce time sheets

This installation is called ‘Tracker’. People say: ‘if it’s not in tracker, it doesn’t exist’. These are the typical agreements that we watch out for when doing implementations at customers. As soon as the team starts to make agreements on what and how to put it in their ‘TenForce’, we know we have crossed the critical mass boundary. Our boundary certainly has been passed already a long time. I just checked our ‘tracker’ and found that we have 16 441 work items in there.

We also have a number of customer specific online versions of TenForce where mixed TenForce/customer project teams use the software for change management, issues, bug tracking. All project meetings are managed by the tool.

Some of the guys in the office are even using it to manage their house construction projects…

Our team leaders arrange, distribute and track work without a need for much interaction. Work linked to plans, meetings, customer requests and so on is passed on to team member’s to do lists. I personally do a lot of this work allocation and follow-up in the evening. A rough estimate is that we need about 3 or 4 hours in total every two weeks to setup and manage the detailed work of 9 people. Most of the items created to manage this work are tasks that take anything from 1 to 4 hours.