I saw and read your links - it seems to be substantiating the idea of being flexible with stories but still keeping the who, what, why questions answered. He joked about the "As" format, but he still ended up confirming it needed to answer those 3 Ws. However I'm more interested on how teams track their work that is not directly a business value\product owner related, such as creating documents, training, new employees etc.

Thank you Barnaby, it seems I always get two very polar answers for User Stories, some say it's only for Business Value, some are more flexible by using alternative stories such as "As a system admin,...". Even on google searches I get different answers, it's seems to just be a style approach.

I'm asking b/c our company wants full transparency through TFS as to what everyone on the team is doing - don't ask lol.

OK I was worried that my PBI didn't really add any "business value" and hence it wouldn't be good the way I had laid it out.

so let's say I was to put 25%, my first question would be what do you tie that capacity to, what Work Item\Task? The rest of that 75% that is "missing", there would be no way to explain that in Team Foundation Server I take it?

The sprints are 2 weeks long, the program increment is 2 months long. As far as the work is concerned that bug was finished in an 2 hours - the requirements documentation is taking about a few business days.

So in capacity if someone was learning the system, getting a p.c. set up, etc., what would you set in the capacity under "Activity"? I don't see "externalities" in the scrum template of TFS.