In Team Foundation Server 2013, there are 3 templates available for team project by default
Microsoft Visual Studio Scrum 2013
MSF for Agile Software Development 2013
MSF for CMMI Process Improvement 2013
All of them agile enough to accommodate your needs, but I think the first two are more convenient.
The Scrum template is designed to support the Scrum ...
What you're seeing is how TFS currently works. I've logged this with the Product Team a couple of times, and I've heard a couple of ways it might be solved in the future, but for now your tasks found and solved on the same day are not reflected.
The funny thing is that the burndown will still be correct. Any hours found and resolved on the same day have a ...
Scrum itself doesn't really define how you're supposed to communicate within the Team. If just non-formally informing QA works for you, great. If not, look into a tool to do it. An important point, though: a story that has not yet been approved by QA should not be considered 'Done'. It's only Done once it's ready to ship to the customer.
A common practice ...
Some teams, especially those that are new to Scrum, use a combination of story points and task hours.
The story points set the capacity of the sprint, but the task hours allow the team to do several things:
Ensures no individual in the team is overloaded in the coming sprint
Ensures that no task is to big (e.g. some teams set a maximum limit of 1 day for ...
Your question is tagged with scrum. Therefore, the answer should be based on Scrum, not the tool you're choosing to use, which in this case is tfs.
You can fix your process problems by:
Participating better in Scrum ceremonies, and sitting with your team.
Tracking progress towards Sprint Goals rather than focusing on utilization. See also: 100% ...
What is the definition of work done in Scrum
Work that satisfies the Definition of Done, which is defined by the Team.
The problem with this is that work being closed on a daily basis is not shown on the Burndown chart
This is the correct behaviour. From Scrum's perspective, an incomplete story provides zero value, so the burndown shows zero progress.
Have you tried using Trello for this? Although we don't have any "permanent" remote workers, we do have several members of the team who work away from the office for months at a time. We have the "Product Backlog" for each product, which the PO maintains and we (as a team) go through this during our sprint planning and pull stories into the "Sprint backlog" ...
I do not know how to tease the information out of TFS, however if you are willing to use another tool that integrates into TFS, I would suggest Eylean Board. It offers time tracking as a feature and generates time reports based on what you need. The reports are generated for each team member individually, including all of the projects they are working on.
This question raises a big question to me - is this actually a project in itself, or something that will be altered as part of other projects? If the latter, it may not need anything around it other than source control.
Removing the TFS element from this question, Kanban is an agile methodology without time boxing that could be applied. These situations ...
Are you sure you want this integrated in TFS?
If your team is agile and is using the Scrum or MSF Agile template, it's not tracking the data required to create the reports your manager would like to see. And if your team is doing agile properly, then it probably doesn't want to track this data in this way.
There are other ways of tracking project completion ...
Your request doesn't really make sense from a purist perspective. In Scrum teams a member doesn't get individual task assignments and team members don't individually move from one sprint to another. In Scrum a team works as a collaborative group, together working on the goal that was set for the sprint.
To achieve the goal during a sprint the whole team ...
Typically you'd use one of three methods in TFS.
Option 1: Area paths
You can use area paths to match up to your major versions. Create a "V2" area path (and the requisite sub-paths) to segregate the work items.
Option 2: Iteration paths
If you aren't using the iteration paths for Scrum sprints, you can also use iteration paths for this purpose. Similar ...
Simplicity--the art of maximizing the amount of work not done--is essential.
Ask why is is necessary to use this extra level of hierarchy. If the benefit can be defined, then the answer to your question will reveal itself.
Often this becomes a way to answer "When will feature XYZ be complete?" Since the Product Backlog is often evolving, it may not make ...
One possible solution would be to take the releases out of the iteration hierarchy and track the releases as tags on the backlog items. Then set up your iteration queries so that the tags appear as a column. This will allow you to see everything in a given iteration at once and see which items within the iteration are going into each of the releases. You can ...
This is not a feature that comes stock with TFS
Depending on your bosses requirements, creating a TFS custom process template may be suitable, depending on how he/she wants to consume the information, e.g., graphs, roll-ups, etc. For more information on custom process templates please reference TFS documentation here.
There are 3rd-party tools out there ...
Kanban is suitable for ongoing work
Kanban is suitable for managing ongoing work that does not have a specific start and an end. Sounds like the work you described is of this nature.
I understand that TFS has a Kanban template. However, I have not used this even though I have used the TFS Agile/Scrum template.
Here are some of the key aspects of Kanban:
I do not use TFS, nor do I have access to the tool, but from looking at the help page. It appears you specify a "flat-list query" that queries completed tasks and visualize that with a "stacked bar chart" while perhaps specifying size in the "Values" field.
If you are looking for a tool that makes TFS more user friendly, Eylean could be a great option. It offers a two way integration with TFS and represents the tasks in a clear task board that can be projected on a big plasma tv or elsewhere.
TFS 2013 has very comprehensive web portal which was not available in previous versions.
In order to see the distribution of developers among different projects, first you have to write the new query. In you new query delete the 'Team Project' clause which comes by default.
Your new query should look like this
Than click run.
The system will bring all ...
As others have said, kanban seems like a good fit based on your criteria. I would also highly advise you to ignore tools and management software when first considering how to most effectively work. :)
I think that starting with a specific tool or tech places too much of a constraint on the initial view of the work, and will limit the potential ...
You can use the Kanban boards attached to each backlog for a continuous flow process.
One minor issue:
In VSO (I haven't tested on latest on-premises TFS), these boards work with Story / Feature / Epic items (Agile process) and Feature / Backlog Items (Scrum process). It means that the Task boards, ...
Hm... This is tough. In my experience it is not useful to put customer requirements directly into TFS as work items of any sort, especially if they are in the form of "20 long sentences". What I would do is this:
Take those 20 sentences and have your designer build a wireframe mockup that completely covers the 20 sentences. This will help you uncover ...
Anyone can create user stories but only the Product Owner can prioritise them. It's also everyone's job to hel refine them to action.
Tracking what's in a release
A single status field on a User Story for environment is not really condusive to understanding either the state of the work item, or it's location in the flow. Ultimately your coders ...
I am not sure what you lose in a single Team Project?
You are either using TFVC which allows you to secure at the folder level, and remove inheritance for greater control.
Or you are using Git which is secured at the Repository level.
Either way you can control which groups of users have access to which code. You can have view only access for some code, and ...
It sounds like you lack transparency and trust with the customer. If each Story represents value for the customer then the customer should approve, view, and order those things.
That said, you can achieve this in TFS. If you create the following Area Paths:
You can secure work items within Internal to be internal ...
Using the "remaining work" field is not a problem as long as you don't mix it with story points. IMO, both are not compatible to one another. Nevertheless, there's still a possibility of using both at the same time for different purposes, e.g. the story points for velocity and the "remaining work" for reporting. Just remember that you might be adding a bit ...
If you are looking to forecast sprints as part of Scrum then i would avoid the user of MS Project at all costs.
You would be better served looking at a Release Burndown or just simply projecting your known velocity onto you backlog.
The former can easily be plotted manually in Excel or on a physical board. It would take less than a minute each sprint to ...
There is nothing scum(ish) about this project
Team members are not involved in deciding what can be accomplished in the sprint. No sprint planning. It is top-down.
No coordination among team members in the form of a Daily Stand-up.
Team is not attempting to create a potentially shippable increment at the end of the sprint.
Team is not showing the work ...