Loading ...
Sorry, an error occurred while loading the content.
Advanced Search
Author
Subject
Message
Special notice only

Advanced Search
  • How about writing stories not from the perspective on an engineer trying to build them, but of someone interested in the core technology associated with the product. Think like those car fanatics that love hearing about the latest and greatest car technology. Does a dual overhead direct injected/hyper-compressed/turbo-charged engine (whatever--It's an example, There's a reason I'm...
    mpkirby Dec 4, 2008
  • We have had exactly the same reaction from some of our senior developers. "Why am I doing my (less capable) colleagues work for them" "Isn't it the managers job to help the less capable individuals on the team" The basic issue is that technical leadership is not rewarded in the company. If you have 3 salary bands Coder -- 40-60k Lead Developer -- 60-80k Senior Design/Technical...
    mpkirby May 6, 2008
  • > > So you excuse PO's from being effected by the laws of task switching, interesting. > Sent via BlackBerry by AT&T The irony of this being sent via blackberry is quite funny. I wonder what you were task switching out to reply to this :-) Mike
    mpkirby Feb 23, 2008
  • Fetching Sponsored Content...
  • Mike Sutton wrote: > > In the first of (hopefully many) discussions about the consequences > of the empowerment quality of Scrum, I want to check out what the > forum thought about meetings! > > I find that since Scrum gives the team the power to do what it needs > to and fewer things (much fewer) are imposed on all participants in > the process, there are so many more meetings to...
    mpkirby Feb 23, 2008
  • Michael James wrote: > > I just went to a London XP pub night and met with a hardcore > XP guy who claims to dislike Scrum. This wouldn't be notable > except that it's happened before. > [--snip--] > As I see it, Scrum is XP's biggest ally. So where > is this resentment coming from? If I was going to pick a cause, it wouldn't be a software development practice. Perhaps if you are a...
    mpkirby Feb 22, 2008
  • CJ wrote: > > Dumb question. If the team is using days/hours to estimate (and > re-estimate) each task per Sprint: > > Is there a cutoff for days/hours per task that's simply too long for a > given 2 week Sprint? For example, an 8 day estimate during this > Sprint. Thanks. We try to limit tasks to less than 2 calendar days and 12 hours. Specifically the idea is that if at the...
    mpkirby Feb 19, 2008
  • stig.efsen wrote: > > Hi, > > trying to persuade customers to implement Scrum I need solid facts that > you (over timer) will get higher ROI/business value using Scrum. > > I searched this group but didn't find what I was looking for. > > Besides Jeff's paper on Systematic (CMMI level 5 company which gained a > lot when inplementing Scrum), can anyone direct me to published...
    mpkirby Feb 19, 2008
  • Mike Cohn wrote: > > Hi Mike-- > I think a burn down chart is a must for 4-week sprints. Very nice in 2-week sprints. > Very likely a waste of effort on one-week sprint. By the time you saw a > trend you'd be done! Our experience is that when you look at the burn down each day as part of the stand-up, there is a focus on the idea of finishing the sprint with everything that you...
    mpkirby Feb 19, 2008
  • Michael James wrote: > > I just went to a London XP pub night Wow. In London they even program at the pub. I'm definitely working in the wrong city. :-) Mike
    mpkirby Feb 19, 2008
  • It seems to me that incremental organizational improvement is as important as incremental software development. The real question we should be asking ourselves is that when we settle for something less than the ideal, what are we going to do next iteration that gets us closer to that ideal. If we ultimately settle for mediocrity and decide that it is good enough, then that culture...
    mpkirby Feb 14, 2008