Scaling Professional Scrum with “Visual Studio Team Services”, Webcast June 27, 2016


Scaling Professional Scrum with “Visual Studio Team Services” with Martin Hinshelwood

Webcast Date: June 27, 2016, 14:00 EST (18:00 UTC)

“In this interactive webcast, Visual Studio ALM MVP and Ranger Martin Hinshelwood enlightens us on scaling professional Scrum with Visual Studio Team Services.”

Tools don’t solve problems, but they can help reduce the friction of Scaling Professional Scrum. The only way to successfully scale across multiple teams, maybe in multiple countries, is to create robust automation and orchestration for minimising the risks, and time, of manual tasks. Visual Studio Team Services allows you to create a robust, platform agnostic, support structure that can start where you are, and grow as your needs mature. One Scrum Team, One Nexus, or many…See how it grows…

Source: Scrum Pulse

Webcast Register Page: https://attendee.gotowebinar.com/register/5828311402116766723

Advertisements

Scrum with Asana in 7 steps | Jose Barato


GREAT POST!   SCRUM with ASANA.

In this post, in only seven steps, I will try to show how I use Scrum with Asana, just by using lists. Here is a short video in Spanish. When I start a Scrum Project, the first thing I do is to create

Sorgente: Scrum with Asana in 7 steps | Jose Barato | LinkedIn

Portable Kanban and Kanban for Outlook Addins


What is Kanban? Is it possible to use it for personal task management? … Sure !

Kanban Board:

Definition here: http://guide.agilealliance.org/guide/kanban.html#sthash.ipfukUPU.dpuf

Source: http://guide.agilealliance.org/guide/kanban.html

Nice book about Kanban: “Agile Project Management with Kanban (Developer Best Practices) 1st Edition” http://www.amazon.com/Project-Management-Kanban-Developer-Practices/dp/0735698953/

Nice Blog here: http://kanbanblog.com/explained/

…….

Below some Applications and Outlook Addins to simulate “Kanban Boards” for personal planning, tracking & control; for teams management the better solution is Always an “Agile Integrated Online Solution” ex: “Kanbantools, Asana, Visual Studio Online and Others good solutions…)

“Portable Kanban” … a great tool by Dmitry Ivanov, free to use.

Visit the post for more:  Dmitry Ivanov

Direct Download link: https://drive.google.com/uc?export=download&id=0BwUfh6wcVgWKVHRDLWtKZy1HUGc

“Kanban for Outlook Addin (2013, 365) from Microsoft”

kanban oilook

Kanban Board is a visualizing tool for the Outlook, which splits tasks upon their status.”

.. a nice kanban addin for Outlook.

Direct Download link: https://store.office.com/kanban-for-outlook-WA104354490.aspx?assetid=WA104354490

my Best Choice !!!   “Kanban Task Manager for Outlook 2″

kanban ADDIN

kanbva 3

kanba excel

.. a great kanban addin for Outlook !! .. the best choice!

Direct Download link:  http://kanban-task-manager-for-outlook.windows10compatible.com/download

Kanban in Visual Studio Online e in Team Foundation Server

https://msdn.microsoft.com/Library/vs/alm/work/kanban/kanban-basics

kanban animated

..another nice free solution is “personal kanban-with-google-spreadsheet”

pkanba2

Direct Download link: http://www.jellybend.com/2013/01/02/personal-kanban-with-google-spreadsheet-and-google-apps-script/

…the last tool.. “my-personal-kanban”… a great free tool with nice cloud support..  : “My Personal Kanban”

My Personal kanban: “This is a one page HTML/JavaScript application for people who would like to use simple and basic Kanban board for their personal stuff”

Direct Download link: http://greggigon.github.io/my-personal-kanban/

..you are welcome !

VSTM (Visual Studio Team Services) Agile Tools


Great updated MSDN help pages about VSTM !

Agile tools : Scrum & Kanban can work fine happy togheter ! …

KANB2

“As a project manager you can plan and track the work required to bring your applications from idea to completion. Agile tools provide you with the power, flexibility, and responsiveness you need to stay on top of changing priorities, deadlines, and requirements.

To use these tools, you need to first create a team project. You can do that either in the cloud with Visual Studio Team Services, or by creating one on an on-premises Team Foundation Server (TFS).”

Overview: https://msdn.microsoft.com/library/vs/alm/work/overview

Summary

Backlogs

Scrum

Kanban

Track

Scale

 

Visualstudio Online: Kanban basics


Visualstudio Online: “Kanban basics”

kanban

To maximize a team’s ability to consistently deliver high quality software, Kanban emphasize two main practices. The first, visualize the flow of work, requires you to map your team’s workflow stages and configure your Kanban board to match. The second, constrain the amount of work in progress, requires you to set work-in-progress (WIP) limits. You’re then ready to track progress on your Kanban board and monitor key metrics to reduce lead or cycle time.

Your Kanban board turns your backlog into an interactive signboard, providing a visual flow of work. As work progresses from idea to completion, you update the items on the board. Each column represents a work stage, and each card represents a user story (blue cards) or a bug (red cards) at that stage of work.

Sample KANBAN Board

Kanban board, Agile template

User stories and bugs correspond to types of work items. You use work items to share information, assign work to team members, update status, track dependencies, and more.

You open your Kanban board using one of these URLs that connects you to your team project:

Visual Studio Online: http://AccountName/DefaultCollection/TeamProjectName/_backlogs/board/

On-premises Team Foundation Server (TFS): http://ServerName:8080/tfs/DefaultCollection/TeamProjectName/_backlogs/board/

If you don’t have a team project yet, create one in Visual Studio Online or set one up in an on-premises TFS. If you don’t have access to the team project, get invited to the team.

Kanban core practices

What is Kanban?  http://kanbanblog.com/explained/

Having worked through the above four steps, you’re well on your way to implementing most of Kanban’s “six core practices”.

  1. Visualize your workflow. Teams track their work using a Kanban board that maps to how they work. Teams discuss how to best focus their resources to deliver the most important work.
  2. Limit work in progress. Teams set and adhere to WIP limits they set for each stage of work. They use WIP limits to maintain focus on completing what they started and to identify bottlenecks occurring in their processes.
  3. Manage flow. Teams monitor the overall work in progress and lead time, which gives them an idea of the speed of their delivery.
  4. Make policies explicit. Teams spell out the standards and processes they agree to follow and make them readily accessible. For example, by making the team’s Definition of Done for each work stage explicit, they can avoid wasted time and effort.
  5. Create opportunities for feedback. Teams meet periodically to reflect on what’s working and what needs improvement.
  6. Improve collaboratively, evolve experimentally. Teams determine how to improve the continuous flow of delivery over time based of key metrics. They involve the entire team to gather insights and ideas. And, when persistent bottlenecks arise, they determine the changes that will alleviate them.

Over time, Kanban can provide your team insight as to how well their current processes work end-to-end and how to improve them. Incremental adoption of Kanban practices tends to yield greater success and builds on the sixth practice, to evolve experimentally. These practices arose from principles of Lean Manufacturing and Systems Thinking.

source  https://msdn.microsoft.com/Library/vs/alm/work/kanban/kanban-basics

Plan and track work, Keep the team focused

A good set of tools will help know which is the status of a given task, how does it contribute to the overarching story or what work has been done until today. Make sure your team checks the tools included on your Visual Studio Online account.

Keep (and honor) your backlog. It wi l help you define the work that needs to be done.
Track task completion on the Kanban board, a visualization that helps the team know what’s in progress, who’s doing what, what needs to be done next and what’s been done.
Break down the work in sprints.
Let the information flow in the team rooms.

source https://msdn.microsoft.com/en-us/Library/vs/alm/Work/overview

Free Online Scrum Master Training and Scrum Master Manifesto


Free Online Scrum Master Training and Scrum Master Manifesto

Free Online Scrum Master Training: The fun way to learn about Agile/Scrum, prepare for Scrum Master certification / Agile certification (CSM, CSPO, PSM, or PMI-ACP), and debunk popular misconceptions.

http://scrumtrainingseries.com/

scm logo

Introduction to Scrum

Backlog Refinement Meeting

Sprint Planning Meeting

Daily Scrum Meeting

Sprint Review Meeting

Sprint Retrospective Meeting

 

Scrum Master Manifesto

http://www.scrummastermanifesto.org/scrummaster-manifesto/A_ScrumMaster_Manifesto.html

“We believe the ScrumMaster is a full-time position for one person on one Scrum team”

scrum master

12 ScrumMaster Pocket Principles…

1.    Dedicated Delivery Improver

2.    Foster Continuous Improvement

3.    Help Continuous Improvement

4.    Empower Coach Deliver

5.    Nurtures The Team

6.    Transparent Team Helper

7.    Commitment To Excellence

8.    Empathetic Evangelistic Guide

9.    Resistant Persistent Dedicated

10.  Help The Team

11.  Awareness Then Improvement

12.  Agile Driving Force

Top 10 things a ScrumMaster usually forgets to focus on (but is not SOLELY responsible for) …

1.    Redefining career paths and goals to be more scrum focussed

2.    Missing Product Backlog items

3.    Team issues aren’t being discussed because they are too uncomfortable

4.    Appropriate balance between end-to-end system test and unit tests

5.    Playing back the team’s progress against the proposed release plan

6.    All tests roll up into the continuous integration results

7.    Team members realise the benefits of refactoring

8.    Code is regularly peer reviewed

9.    Pair programming is being utilised

10.  Definition of done is being expanded

Microsoft Visual Studio Scrum 2013 & MSF for Agile Software Development 2013


Microsoft Scrum Vision

Microsoft Visual Studio Scrum 2013

https://msdn.microsoft.com/en-us/library/ms400752.aspx

MSF for Agile Software Development 2013

https://msdn.microsoft.com/en-us/library/ms400752.aspx

Scrum is a framework for running projects that is based on agile principles and values. It defines a set of activities that can help your team deliver more value to your customers faster. These activities provide your customers with the opportunity to review, guide and influence your team’s work as it progresses. This approach does not attempt to define everything at the start of a project. Instead, your team works in short iterations (also called sprints) and refines the plan as the team makes progress. For information about the agile principles and values on which Scrum is based, see Agile Principles and Values, by Jeff Sutherland.

MSF for Agile Software Development v5.0 is based on Scrum.

https://msdn.microsoft.com/en-us/library/dd997796(v=vs.100).aspx

Agile Principles and Values, by Jeff Sutherland

https://msdn.microsoft.com/en-us/library/dd997578(v=vs.100).aspx

Scrum vs. Traditional Project Management


Scrum vs. Traditional Project Management

This article is very interesting (and very clear) and summarized in a few lines the differences between the traditional PM (Project Management FoundamentalsParameters) and Scrum Vision.

Source from Scrumstudy.com http://www.scrumstudy.com/scrum-vs-traditional-PM.asp

SCRUM Foundamentals

https://www.scrum.org/

https://www.scrumalliance.org/

Scrum in 6 minutes

http://www.scrumstudy.com/scrum-in-six-minutes.asp

Scrum Process Schema

Source http://www.open-ware.org/ita/methodology/scrum.htm

Scrum Principles & Scrum Phases & Processes

Scrum vs. Traditional Project Management Vision

“Traditional project management emphasizes on conducting detailed upfront planning for the project with emphasis on fixing the scope, cost and schedule – and managing those parameters. Whereas, Scrum encourages data-based, iterative decision making in which the primary focus is on delivering products that satisfy customer requirements.

To deliver the greatest amount of value in the shortest amount of time, Scrum promotes prioritization and Time-boxing over fixing the scope, cost and schedule of a project. An important feature of Scrum is self-organization, which allows the individuals who are actually doing the work to estimate and take ownership of tasks.

Following table summarizes many of the differences between Scrum and traditional project management:”

Source from Scrumstudy.com http://www.scrumstudy.com/scrum-vs-traditional-PM.asp

You can find another nice post about Successful Scrum implementation here:

11 Tips for a Successful Scrum Implementation

http://www.implementingscrum.com/2015/04/21/11-tips-for-a-successful-scrum-implementation/

SCRUM Methodology (in Italian Language)

Source http://www.open-ware.org/ita/methodology/scrum.htm

Others nice links here:

MY Better Scrum applications:

Scrumwise, Better Scrum > http://www.scrumwise.com/

Asana > https://app.asana.com/