True in some organisations but in many places a different team takes over once the initial implementation makes production. And KPIs for original development team is frequently just to get the initial version out the door in a timely fashion. Not saying its healthy or Agile (using the good sense of the word) but much more common that one might think.
Paul. On Thu, Feb 4, 2010 at 9:25 AM, Viktor Klang <[email protected]> wrote: > > > On Thu, Feb 4, 2010 at 12:21 AM, Paul King <[email protected]> > wrote: >> >> Yes, I would track features implemented and if I was serious about the >> whole >> thing some kind of metrics around maintenance not just development. > > Interesting that you mention that, > > Poor maintenance will kill productivity, which will drop velocity/lead-time, > so it's kind of implicitly measured. > > Cheers, > > >> >> Cheers, >> >> Paul. >> >> On Thu, Feb 4, 2010 at 9:15 AM, Viktor Klang <[email protected]> >> wrote: >> > >> > >> > On Wed, Feb 3, 2010 at 11:07 PM, jr <[email protected]> wrote: >> >> >> >> But lets assume you are the head of an IT department, you have several >> >> development teams working under you, and you want to define a set of >> >> metrics that will allow you to measure the productivity of the >> >> different teams (and lets assume all teams develop in the same >> >> language). What approach would you take? I understand that measuring >> >> lines of code is misleading, but I fail to come up with a good solid >> >> alternative. One can say that the best metric is to have each team >> >> lead closely monitoring the developers on her/his team, but then we >> >> know that each team lead will report at her/his own convenience. >> > >> > Use Scrum and track velocity or use Kanban and track lead-time >> > >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "The Java Posse" group. >> >> To post to this group, send email to [email protected]. >> >> To unsubscribe from this group, send email to >> >> [email protected]. >> >> For more options, visit this group at >> >> http://groups.google.com/group/javaposse?hl=en. >> >> >> > >> > >> > >> > -- >> > Viktor Klang >> > | "A complex system that works is invariably >> > | found to have evolved from a simple system >> > | that worked." - John Gall >> > >> > Akka - the Actor Kernel: Akkasource.org >> > Twttr: twitter.com/viktorklang >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "The Java Posse" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/javaposse?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "The Java Posse" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/javaposse?hl=en. >> > > > > -- > Viktor Klang > | "A complex system that works is invariably > | found to have evolved from a simple system > | that worked." - John Gall > > Akka - the Actor Kernel: Akkasource.org > Twttr: twitter.com/viktorklang > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
