Planning and Tracking Projects – Part 1

Hello Everyone,
Today we will write about the first step in ALM which is planning and tracking stage, Visual Studio Application Lifecycle Management (ALM) provide teams with the tools to effectively manage the lifecycle to develop applications. As the following illustration shows, teams can use these tools to tell user stories, to manage the backlog, plan a sprint, and run a sprint, to engage stakeholders to provide continuous feedback, and to easily incorporate feedback to support the next iteration of software.

Planning and Tracking Projects

By using Visual Studio ALM, you can manage customer needs more effectively. You can create a high-level plan that breaks your project down into potentially shippable increments, and you can create detailed plans to execute shorter iterations in which you develop those increments. These Agile and Scrum practices are increasingly being adopted by teams because they can be adopted incrementally and applied to almost any project and process. Visual Studio ALM supports these practices with the following tools that enable you to illustrate stories, define product backlogs, plan and run sprints, and engage stakeholders.

  • PowerPoint Storyboarding: You can quickly illustrate a user story, requirement, or experience by using PowerPoint Storyboarding. With this tool you can build a storyboard from a collection of pre-defined storyboard shapes, capture existing user interfaces and customize the layouts of your web pages or phone application, as well as link the storyboard to a work item stored in Team Foundation Server.
  • Product backlog: The product backlog page shows a single view of the current backlog of work that can be dynamically re-ordered and grouped. Product Owners can quickly prioritize work and outline dependencies and relationships.
  • Sprint backlog and team capacity: The sprint backlog page reflects in real time the data you input that includes work items assigned to the iteration path, and specifying dates, individual work capacity, and work interruptions both for the team and individuals. Teams can get instant feedback on the rate of burndown and where they are over capacity.
  • Task board and burndown chart: As a daily practice, the team can view and update the task board to reflect the status of work items visually. The team sees the progress they are making against each product backlog item and can quickly focus on remaining work. Also, integrated into the task board is a real-time burndown chart of the remaining work in the team’s sprint.
  • Request Feedback and Microsoft Feedback Client:  The Request Feedback and Microsoft Feedback Client tools enable teams to engage stakeholders to provide frequent and continuous feedback. The feedback client enables stakeholders to directly interact with working software while recording rich and actionable data for the team in the background through action scripts, annotations, screenshots, and video or audio recordings.

Next post I will talk about the starting point for working with Visual Studio ALM which is create a team project, don’t miss it!

Related Topics | Agile Project Management using TFS 2012

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s