Impediments

1. 

   decioalex
   Member

   Hi, how can we log impediments or bugs to the sprint? I know we should log a impediments backlog and a bug backlog, so we can keep track of everything and maybe add what is necessary to the next sprint, but I fail to see how to do it with this tool.

   Also, it would be nice for the sprint backlog view, to show only what is selected for the sprint, and not the whole backlog. Or at least add something for us to know which stories are in the sprint. Or maybe is there a way for us to see this, and I didn't find it.

   Anyways, this is a great tool so far. I look forward for the next version!

   Thanks.

   Posted 2 years ago #
2. 

   admin
   Key Master

   Hi decioalex,
   Regarding bugs/impediments, based on the habits in the company I'm working for, I didn't develop any specific feature, considering they can be managed in the spare time of the team. When there is an outstanding bug/impediments, then it is tracked as a specific user story in the backlog. Now I agree it's not an ideal situation.

   Ideas to better deal with bugs/impediments:
   * Build a separate product backlog within the same project - I'm not keen doing though, as I fear it will complicate the usage of the tool
   * Support new types of stories within the product backlog : "story", "epic", "spike" then "bug", "impediments"
   * Use the tagging system to identify specific stories as "bug" / "impediments"

   What do you think?

   Regarding the sprint backlog view, it's good idea - I suppose I could see what we can do through filtering.

   Thanks,
   Nicolas

   Posted 2 years ago #
3. 

   decioalex
   Member

   Hi Nicolas, thanks for the reply!

   About the impediments, I was thinking more on the line of other types of stories or tasks and whenever a story or a task is marked as impediment or bug, it could change the bg color to orange and red, for example.
   Is it possible or easy to do with this version of TheScrum? I could see how I could tweek it.

   Are there any plans for your next release? Or do you plan to make the current development stage available for us to test?

   thanks and regards

   Posted 2 years ago #
4. 

   admin
   Key Master

   Hi decioalex,
   Unfortunately, I didn't make much progress on the new version due to personal issue(ski accident...). However, your question makes me want to restart :)

   In the "story" table, there is a "storytype" column: 1,2,3 are used. We could imagine using 4 for "bug", 5 for "impediments". No need to change the DB structure.

   In "class_story.php", we can add the following functions:

   public function isBug() { return ($this->getField('storytype') == 4); }
   public function isImpediment() { return ($this->getField('storytype') == 5); }

   The display is managed in "class_storydisplay.php" (that inherits "class_story.php").

   In "_ajax/story/add.php", you can add the following values to select story type:

   <div><label for="new_story_type4"><input type="radio" name="new_story_type" value="BUG" id="new_story_type2">Bug</label></div>
   <div><label for="new_story_type5"><input type="radio" name="new_story_type" value="IMPEDIMENT" id="new_story_type3">Impediment</label></div>

   Then in "_ajax/story/add_db.php", add:

   case 'BUG':
   $storyTypeID = 4;
   break;
   case 'IMPEDIMENT':
   $storyTypeID = 5;
   break;

   (realizing there is a good code optimization to make there :) )

   That should make it...

   Hope it helps
   Nicolas

   Posted 2 years ago #
5. 

   decioalex
   Member

   Sorry to hear about your accident, Nicolas.
   If you do get back to work on TheScrum, I know there's a lot to be done, but let me tell you that I've tested a lot of applications out there and yes, there are some pretty complete applications around, but yours is the easiest, fastest and most user friendly I've found around. And it's in PHP :)

   There are some features I find lacking, like the ones above, and some optimization that could be done on the backend (maybe using smarty to separate the front end from the backed), but I think you have a really great application already and it could only improove.

   Unfortunatelly, you are not ranking much on google, but maybe by creating a robot.txt file and submiting a sitemap.xml to google, tat could change, along with some more content update on the site, so people would get to know you better and maybe you could have a lot of help too! :)

   There's one question I have, though. Here, I have to use Scrum with multiple projects for the same team. So I was wondering if a good way to separate things better (different products and POs), would be to treat each product backlog as the same project but different epics, with each epic having its own stories. I could use separate projects and backlogs, but that would make it more difficult to manage all the proccess and the Whiteboard/burndown. Your input would be great.

   Anyways, thanks a LOT for the ways to adapt the system. I will get right down to it.

   Regards.
   Decio

   Posted 2 years ago #
6. 

   decioalex
   Member

   Hi Nicolas, I've did the changes you've suggested and it's working great :). The only things is that the tasks created for the impediments and bugs are not colored accordingly (I've changed the class_taskdisplay.php, but couldn't find how to send the story type for the task). This happens on the sprint planning tab. On the whiteboard, also, the stories are not colored and neither are the tasks. How can I change that?

   Thanks!

   Posted 2 years ago #
7. 

   admin
   Key Master

   Hi Decio,
   To color the tasks in the whiteboard, go into "class_storydisplay.php" and enhance the "renderPostIt()" function to support "bug" and "impediment".

   To color the tasks is more difficult... I would suggest:

   In class "class_sprint.php", enhance the "getTasks" function to retrieve the "sto_type" field from the "story" table (joint on "sto_id" column).

   In class "class_task.php", add a getter:
   public function getStoryType() { return $this->getField('sto_type'); }

   Then you should be able to use it in "class_taskdisplay.php"...

   Thanks for the compliment. I'm proud to hear you think it"s the easiest and most user friendly tools you found as that was my main drivers to design it :)

   "multiple projects for the same team" -> I would say the answer would be more in the methodology than in the tool. If you think the team will pick stories from the various projects during the same sprint, then go for 1 backlog with epics. If you think the team will dedicate one sprint per project, then go for separate projects.

   Hope it helps,
   Nicolas

   Posted 2 years ago #
8. 

   decioalex
   Member

   Hi Nicolas, thanks for the inputs. I will try this out.
   I can even make available the changed code, so you can have a look on it, if you want.

   One other doubt. If I nned to include any other input field on the task create pop, how can I make the values available for the add_db code? I couldn't find anywhere where we can actually check the submitted value and what is being sent.

   Thanks for all the help!
   Decio

   Posted 2 years ago #
9. 

   admin
   Key Master

   There is a generic code to manage all forms. It's done through "object_add.php", "object_add_db.php" and "common.js" -> basically when you add a new field in the form, its value is directly available in the add_db code.

   I'm interesting by your code and screenshots, so that I can embed it in the next version of theSCRUM :) You can send me those info at contact AT nicolasleroy DOT fr

   Also, would you be interested to write a little "testimonial" about your usage of theSCRUM ? I could publish it through the blog. It could be interesting for other people to learn how it used in other companies.

   Thanks for your help and support,
   Nicolas

   Posted 2 years ago #
10. 

    decioalex
    Member

    Hi Nicolas. It was harder than I though, but I think The system is working with the enhancements done.
    The only thing I would still like to see is a separation on the sprint backlog to show only the items in the current sprint, as well as a log of previously done sprints, for reference and follow up.

    With the modifications done, we can now add Impediments, Bugs and Unplanned stories to the Product Backlog, as well as the same types for each task. The sprint planning window shows the task type and colors each one accordingly (if it's a bug task, for example, or a bug story, it colors itself with a reddish hue).

    So now there's more visual way of identifying, right on the whiteboard, or sprint planning window, what exactly is happening on the sprint.

    I still need to test using an Epic, as a different backlog for the same sprint (since here we have the situation of the same team working on stories from different products on the same sprint, as well as having only one product backlog and different teams taking care of different sprints (which happen at the same time). So I still have no idea how this would be adapted to the system.

    I will email you the code for your review. :)

    Regards.

    Posted 2 years ago #
11. 

    admin
    Key Master

    Hi Decio,
    The support of bugs and impediments has been added in theSCRUM 0.55.
    Thanks a lot for your contribution
    Nicolas

    Posted 2 years ago #

is released under the MIT license.

© 2012. the-scrum.org is powered by bbPress. Theme design by WPShoppe.