Corporate Coder

As I last posted we are going ahead with our Kanban for Change tickets.  The visit with David Anderson (who wrote Agile Management for Software Engineering...) and Corey Ladas (His Blog is Lean Software Engineering)  really helped focus what we'd like to do at my place of work.  While have similarities, we do have some differences that I wanted to post on.  First thing we want to attempt is to do all our Kanaban electronically.  The feedback Corey gave me was that their group preferred the physical Kanban.  Like David and Corey we want to keep our data in Team Foundation Server.  But unlike their group, we don't want to do double entry.

 Our other issue is that our changes come to us in another help desk system.  This is used Company wide, and we have to use it.  So ideally we want to have a system that flows our changes from the help desk system, to Team Foundation Server.  From there our developers will enter status.  And our reporting will come TFS. 

That's where we'd like to be.  Right now, we are reporting off the help desk software.  And we are attempting to use statistics based on cycle time (how long from when we get the change ticket, until it is resolved).  And also on where those tickets are coming from (what internal applications are generating lot's of tickets).  From this information, some applications may warrant an upgrade project, before we had scheduled that.  We also want to get that information visible to the development team so they can see how quickly things are turning around.