Posts Tagged ‘Backlog’

  • Dealing with a different type of backlog…your bug backlog

    on Feb 3, 11 • by Todd Landry • with 2 Comments

    Dealing with a different type of backlog…your bug backlog

    As a product manager, the only backlog I typically care about is my product backlog. Do I have the right stories in there? Do the stories have enough detail? Are they properly prioritized? You know, that kind of stuff. Today, however, I’m going to write about a very different backlog, that is the static analysis defect backlog. A static analysis backlog is created when you run a static analysis product on your code base for the very first time. Chances are pretty good that the first analysis is going to list a large number of defects,

    Read More »
  • Going Agile Part 3 – The 1st Iteration Planning Meeting

    on Jan 14, 10 • by Todd Landry • with No Comments

    Going Agile Part 3 – The 1st Iteration Planning Meeting

    Now that the New Year is upon us, I thought it would be a good time to add another chapter to my Going Agile series. My last entry left off at the point where we had prepared our backlog, created team rules and defined “Done”. Now we were ready for our first Iteration Planning meeting. In our “team room” we had all the essentials in place for this meeting: stacks of color-coded cards (for capturing the various to do’s, or tasks), pens and highlighters, our Scrum board (with pins) to stick our tasks onto, and

    Read More »
  • Embedded Systems Engineering – German 2009 Edition

    on Dec 10, 09 • by Todd Landry • with 1 Comment

    Embedded Systems Engineering – German 2009 Edition

    Just wrapped up a successful 2 day Embedded System Engineering conference in Stuttgart, Germany. This “all-German” show had just shy of 600 attendees, as well as about 60 individuals (representing the 20 or so companies exhibiting), so this was considered very good by the show organizers (who by the way did a fantastic job… the food here, for example, was as good as I’ve ever seen for such an event). The Klocwork booth was shared with our good friends at Emenda, and we had a choice spot that allowed a good flow of people. We

    Read More »
  • Going Agile Part 2: Preparing for Iteration 1

    on Oct 20, 09 • by Todd Landry • with 1 Comment

    Going Agile Part 2: Preparing for Iteration 1

    In part one of Going Agile,I talked about how we introduced Agile to our development team. This next post will look at the events that led to our first iteration planning meeting. During the weeks that led up to Iteration 1, there was much work that went on as a team, and much that each team member did individually. As the Product Owner, my biggest task was to create a backlog. Sure, I knew what the main new features were going to be, but I still needed to capture this, and add other oft-requested features

    Read More »
  • Prioritizing your Backlog

    on Jul 16, 09 • by Todd Landry • with 1 Comment

    Over the last few weeks, we’ve been working on cleaning up our product backlog, and the one thing that I always find to be the most challenging is the prioritization. I’ve worked on a number of different products over the years, with a number of different teams, and have used a number of different methods to prioritize a backlog, and I thought I would take a few minutes to share them with you now. 1)    Feature rating – This is the method where Excel really shines, because you get to create a cool matrix consisting

    Read More »
  • Bugs and your Backlog

    on Jul 7, 09 • by Todd Landry • with No Comments

    There was a recent blog on whether or not you should have bugs (that were not found during the most recent iteration) added to your product backlog, or kept in a separate bug backlog. Here at Klocwork we have a defect database that is closely monitored by Support, dev, PM, and so on…suffice it to say, it has a high degree of visibility within the organization and will probably never go away. Being an Agile company we also have a product backlog that is reviewed daily and prioritized regularly. Every two weeks (coinciding with our

    Read More »
Scroll to top