scrumsprintmonitor Issue Tracker Rss Feed

Reopened Feature: Include current work item state in the burndown charts [4952]

PombeirP — Fri, 14 Jun 2013 06:48:00 GMT

Reopened Issue: Time available seems way off [5207]

PombeirP — Fri, 14 Jun 2013 06:48:00 GMT

The Time Available has the <=, but the Ahead of Schedule does not. Our current sprint will end on Feb 16. That leaves 12 work days. We have 4 team members with the same entry in team-info.xml:

<team-member name="Gauthier, Paul"> <time-zone>Central Standard Time</time-zone> <workday> <start>07:00:00</start> <end>14:00:00</end> </workday> <lunch> <start>11:30:00</start> <end>12:30:00</end> </lunch> <avatar provider="gravatar.com" key=key@key.com /> <display-alias>Paul</display-alias> </team-member>

The unassigned member has the same hours. This should give each team member 6 hrs per day - any outlook busy time to dedicate to the sprint. So, even if everyone had the whole 6 hours to use, I thought it would be something less than 12 work days * 4 team members * 6 hours per day = 288 hours. We show <= 449 and ahead of schedule by 268. I also noticed that if I reduce the work day by one hour in the team-member file, both the Time Available and the Ahead of Schedule By values go up 24 hours. I think it should change by 12. I have double check the sprint config file and the Sprint work item in TFS.

I'll keep looking. If no one else is having the trouble, it's likely something in our config files. Although I don't think the team-info.xml was changed at all and the sprint config was just updated to the current sprint. I'll let you know if I find anything more.

Thanks for your help and thanks again for a great tool.

Reopened Feature: Store default credentials [5448]

PombeirP — Fri, 14 Jun 2013 06:47:55 GMT

It would be a nice addition if one can store credentials for the tfs on the local system.

Closed Feature: Include current work item state in the burndown charts [4952]

PombeirP — Thu, 16 May 2013 07:57:13 GMT

Closed Issue: Time available seems way off [5207]

PombeirP — Thu, 16 May 2013 07:57:13 GMT

Closed Feature: Store default credentials [5448]

PombeirP — Thu, 16 May 2013 07:57:13 GMT

It would be a nice addition if one can store credentials for the tfs on the local system.

Reopened Feature: feature suggestions [9316]

PombeirP — Thu, 18 Aug 2011 23:36:00 GMT

Awesome tool. I used to use Telerik's WIM, but without access to source code or any customizability it wasn't proving very useful. This one, however, shines on both counts.

Couple feature suggestions:

1. When a team member is not found in the TeamMemberList (inside CreateTeamMember) return null instead of throwing. This allows me to restrict which team members I show through the team.xml file. Why do I want to do this? I don't, for instance, want to show PM work items or bugs -- I'm primarily interested in showing dev/test. Or I, as the dev lead, want a display outside my office that shows only the status of my devs. With this simple change I can do that. (I've already done this on my local version of the sourcecode.)

2. Integrate http://www.mountaingoatsoftware.com/alt-releaseburndown style reporting for the burndown. This would bemuch more useful than what's shown right now. I haven't tried tackling that yet.

3. Allow slideshow reporting of multiple iteration paths. This would allow a single display for multiple scrum teams.

4. Allow more flexibility in choosing what WI types get included in the report. Looking at "TeamMembersListViewModel.cs:596" you're selecting only SprintBacklogItems. What if I want to include bugs? Suggest modifying IWorkItemAdapter to have a "ShouldIncludeInSprint" property -- will be more flexible. Also a change I've made on my local copy. (Update: there's actually a few places in code where you do w.Type == WorkItemType.SprintBacklogItem -- that really ought to be up to the process adapter to decide. (I suppose I could just make the WorkItemAdapter return SprintBacklogItem for a Bug... but that seems more like a hack than a by-intent workaround.)
Comments: ** Comment from web user: PombeirP **

Commented Issue: Bug in ProcessSprintBurndownForDay [9315]

PombeirP — Wed, 17 Aug 2011 23:37:50 GMT

There's a bug in this function (SprintBurndown.cs:207). When it counts up remaining work, it counts WIs that are in Done state -- I think it should exclude those. Sometimes (especially with the TFS build system) you can check in work against a work item without updating Remaining to 0. The WI gets closed by the build system and should be considered Done.... (and is marked Done by the process template adapter)

suggest modifying line to:

var teamWorkItems = workItems.Where(w => w.Team == s && w.State != WorkItemState.Done && w.State != WorkItemState.Deleted);
Comments: ** Comment from web user: PombeirP **

I guess I never came across that situation because our process template takes care of automatically setting remaining work to 0 if the status changes to Done or Deleted.

Closed Issue: Bug in ProcessSprintBurndownForDay [9315]

PombeirP — Wed, 17 Aug 2011 23:36:47 GMT

Closed Feature: feature suggestions [9316]

PombeirP — Wed, 17 Aug 2011 23:06:00 GMT

Commented Feature: feature suggestions [9316]

partnerinflight — Tue, 16 Aug 2011 23:24:15 GMT

Yup, makes sense. Thanks again for developing such a great tool!

Commented Feature: feature suggestions [9316]

PombeirP — Tue, 16 Aug 2011 23:12:13 GMT

I understood your point, and I can see that its a good idea to abstract the work item type if we have a conceptual need for it. It's just that until now the template adaptor has served just one purpose, and that is to abstract differences in the data representation of each process template. What you're proposing to do now is to expand the concept to also have some kind of intelligence in how you interpret each work item. You could potentially end up with multiple process template adaptors for a single process template, something that would not have made sense at the time I designed this. I'm not saying it is wrong, merely explaining the current rationale. I will give it some more thought when I have some spare time to dedicate to the project. Thanks for the input though!

Commented Feature: feature suggestions [9316]

partnerinflight — Tue, 16 Aug 2011 18:13:48 GMT

Thanks for the response. Some comments:

re point 3: As long as the feature team is prominently displayed in each slide I am not sure this'd be much of an issue. Problem is without this functionality the tool cannot be deployed on a project level (say in the hallway on a large flat-screen.) Thus its usefulness is decreased.

re 4: actually I must confess to misusing the tool somewhat. We do not currently have a true scrum implementation on our team, rather we're more ScrumBut -- we have a stabilization period. So I'm using the tool to display the progress of the stabilization -- how we're progressing against incoming bugs, etc. I could potentially just make a separate template for this use, but from an API flexibility point of view I do think you have a design issue -- if you're going to delegate to work item adapters to interpret a particular TFS entry, it would (to me) make more sense to to allow them to decide whether a particular entry should be counted on a wider scope of attributes than just WI type... having a function in the interface gives you that flexibility. Returning SprintBacklogItem is a hack -- if I wanted to, say, exclude Test or PM WIs from the tally, I'd have to "hack" them to return type as Unknown or something. See what I mean?

Basically I see this tool as something more than a mere sprint monitor. It could easily become a Project monitor, independent of what process you're following.

Created Feature: feature suggestions [9316]

PombeirP — Mon, 15 Aug 2011 21:57:06 GMT

Created Issue: Bug in ProcessSprintBurndownForDay [9315]

partnerinflight — Mon, 15 Aug 2011 17:17:54 GMT

Closed Issue: Resolving Tfs Servers and Projects [8369]

PombeirP — Thu, 17 Feb 2011 22:20:09 GMT

I poked around an noticed that in ConfigurationViewModel.cs PopulateTfsServerNamesList it runs a loop from version = 8 and increments from there. In my case, I had older versions of TFS Team Explorer settings in my registry that weren't used anymore. Because of that, it would pull the old projects I used to connect to from version = 8 but would not pull in the new projects from my TFS 2010 settings.

I was wondering...would it make more sense to attempt to read the settings from the newest version first? Also, instead of stopping as soon as at least one project is found, continue through the version settings to see if there are anymore. I suppose that would have difficulties itself because there could be duplicates from one version to another.

For my case right now, I changed the code to start at version 10, then it pulled the current settings for TFS 2010.

Just thinking as I type. ;-) What do you think?
Comments: Resolved with changeset 61615.

Created Issue: Resolving Tfs Servers and Projects [8369]

PombeirP — Thu, 17 Feb 2011 22:19:23 GMT

Commented Issue: Unable to select my TFS server [7206]

kootsoop — Thu, 17 Feb 2011 21:08:55 GMT

My TFS server is not in Server list. i have just "tfs08.codeplex.com"
But VS is intalled and used with tfs to store my source code.
Comments: ** Comment from web user: kootsoop **

@PombeirP: That seems to fix the issue on my installation. Thanks!

Commented Issue: Unable to select my TFS server [7206]

PombeirP — Thu, 17 Feb 2011 18:10:17 GMT

My TFS server is not in Server list. i have just "tfs08.codeplex.com"
But VS is intalled and used with tfs to store my source code.
Comments: ** Comment from web user: PombeirP **

Can you try the suggestion I gave in http://scrumsprintmonitor.codeplex.com/discussions/224647, and let me know if that works?

Commented Issue: Unable to select my TFS server [7206]

kootsoop — Thu, 17 Feb 2011 03:49:14 GMT

My TFS server is not in Server list. i have just "tfs08.codeplex.com"
But VS is intalled and used with tfs to store my source code.
Comments: ** Comment from web user: kootsoop **

I have a VS2005 and VS2010 installation, and I'm just seeing the VS2005 TFS server.