Bing Developer Assistant Beta extension for Visual Studio



Testing Agile Development, Code Sharing, Sublime Editor and Git with Visual Studio Online

  1. Created a new project in
  2. Choosing a Project Workflow:
    1. i selected MSF Agile
  3. Git integration:–Part-IV-Source-Code–Git-Repository–Wrap-up
  4. While creating project simply select Git as the Source Control
  5. Here’s the project:
  6. Q: how to make visual studio online project public
    1. Can;t right now

Note that before openign the project in VS from the browser directly:

1. Change the Source Control Provider to VS Team Foundation Server in VS 2013 options

2. Note, before you can use the command line, you’ll need to enable basic authentication for your account.

Also, once the project opens in VS, open team explorer and it’ll prompt you to clone the repo for this project ..

If you’re not useing VS, use the code tab in browser for details:

From the command line
You can clone the project using the following command:
Note, before you can use the command line, you’ll need to enable basic authentication for your account.
Moving on,
create a new project and push the code changes
Next, go to the Work tab in the browser and add items to worklog it turns out that i’m using the MSF Agile Type of Project, while the video (Ref: i’m following uses VS Scrum..
The inconsistency is that mine shows features and stories in the Work Tab, while in video its Backlog and Features, which is what i want…
Created New Project:
Now check in initial code and then go to the Settings tab in browser and set Iterations.. note that here you can make a hirerchy of Release and Sprints within each rel…
Make sure the checkbox next to all Sprints and releases is selected, as it signifies that its active…
Return to the Backlog and add items to it..
Then simply drag the items into sprints
Note that herer, unlike Jira, a backlog can have multiple tasks in it..create these from the Board view when u clk on the sprint
Here, it shows how to easily run queries on the project in Excel using the Team Tab..
Note that all the data can be updated directly from excel…
SADLY, the code checkin against work item that is there for TFS is not available for Git yet….so this was a waste….AS IF I CANNOT LINK MY COMMITS TO WORK ITEMS, THEN THERE IS NO POINT REALLY…
ok SO I FOUND THAT Git lets you link work items to commits by using the Commit link type. To learn how, see Manage and commit your changes. ( ) i’m good now….

Settings in Jira Agile Scrum Board

1. I changed the swimlines to Assignees to clearly see who’s doing what at any time

2. In Reports, i find the Cumulative Flow diagram to be the most helpfule to visualize the status of tasks and project as a whole

3. Changed the card color to Priority to know what is most imp

4. i follow this that in the stand-up meeting, i flag the tasks for today (rt clk and flag) so that people know who’s doing what

Agile Gems

  1. Task
    1. Something that is binary: inProgress OR Done
    2. >30 Min but ❤ Days
    3. No waiting on other dependencies…
  2. Scrum
    1. Something with Fixed Release date/ Deadline
    2. Date is more imp than stuff in it
  3. Kanban
    1. Support and Svc team
    2. No Plan or Sprints. No Date Deadline
    3. Just a Prioritized list of tasks
  4. Scrum Planning
    1. Start by creating a list of all the things that you want to do. This is called a BackLog. Assign Story Point to each Task (1 Story Point = 30 Min)
    2. Next Create Epics, which are simply tags/themes that classify tasks (Eg. Books to Read). It is used for filtering.
    3. Next simply move the tasks that u want to do in the next sprint from the Backlog
    4. 2 week sprint is a standard
    5. When the sprint is ready, move from the Plan to the Work mode
    6. Here simply move stuff from Not Started to In Progress and then Complete State
    7. Burnout is the chart of Story Points of this Sprint and the Track Progress
    8. Velocity is the no. of story points that you covered in a Sprint

Ref:  Slides:

Steps for Jira Agile Scrum



1. To attach Epic Tag to issue, don’t create it the regular way. Use the “create issuse in epi” option

2. Story is also like a Bug ie a Issue Type

3. To assign version to issues like i have, mention them in the “Fixed Version” property while creating issue

4. note that u may select multiple issues and rt clk for bulk options

5. Label prop in issue can also be used to tag issues, but that filter is not available in the Plan View, as shown above…hence i’ve used Epic for now, as a label only…

6. for adding Custom Issue Types

THis is what Atlassion has to say:

Plan Mode

Close detail ( T )

Manage your backlog

  • Create and prioritise stories in your backlog
  • Estimate in story points or time

Plan your product development with epics and versions

  • Use epics to track related stories across sprints and versions
  • Assign stories to versions; track release progress
  • Quickly drag-and-drop stories to epics or versions
  • Filter by epics and versions for targeted views of your backlog

Create and launch development sprints

  • Plan multiple sprints in advance
  • Start a sprint, then go to Work mode to move stories through workflow

Learn more about Plan mode and Work mode

Jira Agile Workflow

Jira Agile
Note that GreenHopper is now called Jira Agile and can be accessed from jira (clk on ur name and then agile and then scrum)
Note that for dev, use scrum and for ops use kanban
Quick Start:

Jira AddOns:

Jira Tips
1. Go to Admin section of project and create components (DB, Svc, UI)
2. Go to Admin section of project and create Versions
1. C to create issue
2. . on the issue page to perform operations on it like type ‘log’ to log time for issue
1. project = WMENGGUACS AND status = Closed ORDER BY priority DESC
2. Use Advanced Query option for even easier query creation using type project = …
3. Any search query can be saved to dashboard as result list or as chart
1. the way I do this is to simply create a blank dashboard like one names “Issue Tracker” to track open issues across all projects
2. Next start writing queries in search page, like: project = WMENGGUACS, then on View Menu select “Add to Dashboard” then go to Pie Chart and select “Resolution” as the key for chart
3. ANOTHER WAY IS TO simply clk on ADD GADGET on the dashboard and add all sorts of gadgets. Note that the above requirement can be easily met using the “Issue Statistics” Gadget