TargetProcess Product Blog

Fantastic. That helped a lot. I had actually tried that on a previous install, but for some reason, the columns didn't show up. Not sure if I did something wrong or what...but it seems to be working now. Thanks! (particularly for the fast reply)

The screenshot on this post has an "In Progress" column...how did that get there? Was that a feature of a previous version of TP? Is that a customized view of the Task Board? I would LOVE to be able to customize the view of the task board by adding a couple of columns, but I can't seem to figure out how to do it. Any guidance would be greatly appreciated. We're currently trying out the community edition (On Site), version 2.16.7.14853.

To have In Progress column, you need to add In Progress state for Task. It can be done in Admin -> Process -> Workflow -> Task -> Change State.

I think you have a fundamental misunderstanding of the daily scrum meeting.


At the daily scrum meeting the scrum master asks everyone in the team the three Scrum questions:



* What did you accomplish yesterday?

* What is your goal for today?

* What is getting in the way?



The goal is to focus the team members on what they should be doing, to recognize the need for communication between team members, to recognize when people are working on things which do not lead to the goal of the Sprint, and to recognize the need for escalation when something is getting in the way.



It does not serve to monitor where people are in their tasks, except maybe near the end, when we'll review the state of each task in the "Après Scrum"



We have been using TP for about 3 Sprints now to manage the backlogs and the bugs.



Before we were using a combination of Excel for the backlog and the daily scrums and the wiki for task documentation.



I like TP for managing stories, tasks, and iterations. What TP lacks is easy, strutured access. Things kind of get swallowed by TP which did not happen on the Wiki.



My excel spreadsheet for the daily scrums has 5 columns: Name, Yesterday's Plan, Yesterdays Actual, Todays Plan, Impediments. (If I were managing part time people, I would want additional, corresponding fields for hours worked. Excel is really easy: click on the cell and enter the data.



I do like the idea of the task board. But the taskboard is not primarily for the daily scrum meeting, but to provide everybody at a glance an overview of what people are doing and how the Sprint is progressing.



I would see the taskboard as being projected permanently on the wall. So it should update itself automatically.



It should be configurable on the level of detail, perhaps with different "styles" depending on whether it is being used by a team member to update his status or the dashboard display to monitor the overall state of the sprint.



Remember, Scrum is a starting point. Everybody tunes it their own way through the retrospective process, so your solution needs to reflect these variations (for instance, we allocate user stories to developers, but do not usually plan individual tasks. That is done verbally by the team on a day to day basis. Not dogma, but it works for us). So a customer might want more or less detail or even custom fields on the taskboard.



BTW - I like the taskboard as presented by Henrik Kniberg in his article: Scrum and XP from the Trenches

Hello, Michael D.


here is my feedback for the new feature "TaskBoard" to do the daily scrum:



**first: to much details!

**second: focus on user stories is not helpflul, cause daily scrum should answer questions like "Who is doing what" and not "What is done by whom".

**third: there is no place for impediments



Futher you should keep in mind thats a 15 minutes issue to do the daily scrum. If i would use the TP task board for a daily scrum with 8 team members its more realistic to calculate 30 minutes.



In my opinion a simple board with not more than 4 columns with less informations is more helpful:



1: Who? (Name) - list of all assigned team members

2. What did you do yesterday? - a read only field with the notes of yesterday

3. What will you do today? - a simple imput field to document things by the scrum master

4. Are there any impediments in your way? - again just a simple input field



We do not what micro management at all. TP tends to grow and getting blind bend.



Cheers, jo|ce