Skip to main content

Visual Studio Team Services - Agile - Scrum Project Management Tools

Before starting this article let's understand what is Agile and Scrum. 
What is Agile
Agile is a Method of project management that is characterized by dividing module in to tasks and tasks into short phases of work and frequent reassessment and adaptation of plans. In other words, Agile is a Time Boxed incremental software development method. 
What is Scrum
Scrum is an incremental agile software development framework (Agile Framework). 
Agile Scrum Process in Short.
  • Product Backlog: A product owner creates a customer’s wish list and prioritized it and create backlog, called Product Backlog.
  • Sprint Planning: In this meeting team select small part or module from the Top Priority Wish List of Product Backlog and prepare a small task list.
  • Setting Capacity and Sprint: Team has to deliver the tasks in 2 weeks or 4 weeks sprint, here Scrum Master bind tasks with Time and User.
  • Scrum Master’s role: Is to make sure team focused on its goal.
  • End of the sprint: We have completed tasks which we can Release to Client.
  • Sprint review and retrospective: sprint ends with a sprint review and retrospective where Team Inspect and Adopt to become more effective on process.
  • Next Sprint: In the next sprint, the team chooses another Module and Task of the product backlog start working on the next sprint.
What Setup Visual Studio Team Services
Visual Studio Team Services is a services for track work of team, share code and incremental project release. It’s free for up to 5 Members, you can purchase plan as per your need.
Visit this Link and complete the Sign-up process. 
 
After login it will redirect you to Dashboard, here you can create a Project and Team. Create new project by clicking on 'New' from Recent project and teams.
 
Create your Team Project: From the Process Template you can choose Agile or Scrum Template.
 
From the Version Control you can select Team foundation Version Control or Git. Enter project name and click on 'Create Project' - Select 'Manage Work'.
 
Here I have created 2 templates one using Scrum Template and another with Agile Template.  
                                   
 
 
 
Agile Template
 
 
The Basic difference here is some keywords, like here in Scrum we have Columns Like 'New'. 'Approved', 'Committed' and 'Done' and in Agile Template we have 'New', 'Active', 'Resolved' and 'Closed'. Also for the Backlog in Scrum we have 'Sprint 1', 'Sprint 2' Etc. and in Agile we have 'Iteration 1', 'Iteration 2', etc. You can also change and customize this column as per your need. After creating project, Next task is adding Resources or Users, for that follow below steps.
Go to Users Tab - Add User Details and click on 'Send Invitation' Button,
 
 
 
After Creating Users, next step is creating Backlogs of your project. Click on 'New' and add your 'User Story' in Backlog, set your Prioritized list of works. 
 
 
In your User Story, you can add details of tasks, Acceptance Criteria, Status and Priority, Links and Attachments, as in the following screen.
 
 
Backlog have Board, where you can keep track and manage your Project Progress by simply drag and drop Tasks in Column, Edit Tasks, etc.
 
For Agile Template you can set dates for each Iterations as in the following screen,
 
You can set Capacity, No. of Days of Your Team members for the respective Iteration or Sprint.
 
 
 
You can check also sprint burndown chart. In any point of time you can check the history of your Task as in the following screenshot. Here you can check who task owner is and who has made changes with date and time.
 
 
 
So, this is the overview of Visual Studio Team Services Project Management Tools. 
 
Summary
Main issues with Traditional Project Management
Why do we need Scrum in the first place?
So friends, what are you waiting for, set your own working rules and be a rule player. Start working smartly using Visual Studio Team Services. We will discuss more features like Query Editor, Graph, etc of Visual Studio Team Services and other tools in next article. 
Thank you for reading this article, hope you like it. 

Comments

Post a Comment

Popular posts from this blog

User Story In Agile Scrum - By Ankur Mistry

In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the  Agile Manifesto  says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well.   Reference:https://mazoea.wordpres
Post a Comment
Read more

The Burn Up Charts In Scrum By: Namrata Parik

I would like to propose a less-taken path in my maiden article to track the progress in scrum. We usually do it using the burn down chart which is relatively easier to understand as compared to the burn up chart. These charts help the team and stakeholders to see and track the progress at any point in the release process or sprint. Burn-down chart provides us the information showing the progress based on the remaining hours or story points from top to bottom. (The burn-down chart can be plotted using story points, task count or the remaining effort) This chart is a plot of expected remaining and actual remaining, this is the most used chart in scrum and since it has only two lines it is considered to be a simple chart. It does not cover the scope creep. So sometimes what might look like ‘no work ‘ done by the team may actually be a result of scope creep. The chart below reflects that the team has not done any progress in Sprint 5 and 6 as the story points remain the same. Image
Post a Comment
Read more