Quick reference poster--the VSTS Rangers “scrumified“ process

from: Certified Scrum Developer course … we can finally remove the duck tape :) The Accentient Scrum Developer course is an intensive five day experience for whole teams of developers. The course teaches teams how to turn product requirements into potentially shippable increments of software using the Scrum framework, Visual Studio 2010, and modern software engineering practices. Attendees will work in self-organizing, self-managing teams using a common instance of Visual Studio Team Foundation Server 2010 to achieve this goal.

VSTS 2010 TMap process templates infographic

Been playing a bit with the creation of infograpics, this is one I created about VSTS 2010 and TMap, what are the benifits of using them together and how are they connected. This one isn’t finisched / approved yet (so not donwloadable in full format:-), need to change the screenshots and text in several places. But, the idea is to have them printed on a placemat with on the back contact information and to make notes.

VSTS 2010 Test Edition at the TMap® Dag 2009 [Dutch]

Theorie en praktijk wisselen elkaar af met onderwerpen als TMap NEXT®, ketentesten, security testen, Agile testen en nog veel meer actuele onderwerpen. Tijdens de TMap® Dag 2009 wordt het nieuwe boek TPI® NEXT gelanceerd! Een compleet herziene versie van het TPI® model waarin voor het eerst de business doelen écht een ssentiële rol spelen. WS8 -- De TMap NEXT® Proces template voor Visual Studio Team System Gerard van der Pol, Microsoft Visual Studio Team System ondersteunt uw procesbenadering voor software ontwikkeling door het gebruik van Proces Templates. De guidance en werkwijze kunnen hierdoor transparant worden ondersteund door de in het project gebruikte tooling. Voor de nie... [More]

…and another Team system MVP in the Netherlands

          Pieter just pinged me that he is awared as Team System MVP…                     He already updated his LinkedIn page: but not his blog :-) great news…  congratulations Pieter!!! [lets go skiing during the mvp-summit!?]

How to keep you fingers on the keyboard within VSTS 2010 Architecture Edition

Keyboard junkies have a hard time with all that dragging and dropping of shapes and connectors around within VSTS 2010. So here are some tips for these junkies how to keep you fingers on the keyboard. New default DSL Tools behavior… Adding shapes to the design surface allows you to directly start typing, for example after adding a class shape to the design surface lets you start typing the class name. Hitting 'Enter’ will confirm the value and F2 lets you edit it again. More interesting, in the compartments of the class shape hitting Enter twice adds an attribute or operation.  So, type a name for an attribute, hit Enter to confirm the value and hit Enter again for adding a new att... [More]

SDL ‘Merged’ Process Template White Paper.

The SDL group just released a paper which describes the steps [seven easy steps] you need to take to merge the SDL specific process items with your existing process template. Two New Security Tools for your SDL tool belt (Bonus: a “7-easy-steps” whitepaper) Very nice work… Hopeful we get in the future the possibilities to merge process templates in a less manual way, but this works. The steps described in this paper are based on unfold process template so you have to take this steps for every new project you create. An other way to merge template is by providing the XML and manually merge it with your existing template. A possibility described in this post “VSTS 2010 TMap Process Temp... [More]

03: Agile Testing Business Whitepaper.

My colleague's in Ireland wrote a great paper about Agile Testing practices… ‘ At its heart, agile is all about quality and focusing on the customer. Testing therefore has a significant role to play within an agile development environment and can actually strengthen the output of the process.’   Part 00: Agile Testing with VSTS 2010 and TMap Part 01: User Stories 02: Management, preserving and organization of manual test cases within VSTS 2010. 03: … this post 04: … [probably] 2.1 test case management practicesvar dzone_url = 'http://www.clemensreijnen.nl/post/2009/09/11/03-Agile-Testing-Business-Whitepaper.aspx'; var dzone_title = '03: Agile Testing Business Whitepaper.'; ... [More]

02: Management, preserving and organization of manual test cases within VSTS 2010.

Part 00: Agile Testing with VSTS 2010 and TMap Part 01: User Stories [current post, removed the Agile Testing blablabla and part pre-fix] This post belongs to the series of “Agile Testing with VSTS 2010 and TMap” although this topic has a wider scope, in used software delivery methodology you have to think about test case management. A small introduction. First a small introduction to give some direction on the needs of test case management. The drawing below I made during a discussion with several TMap experts and explains how test cases are created and executed in a simple situation. From top to bottom and left to right. Teams start brainstorm o... [More]

Enrich VSTA 2010 Use case diagram with SketchFlow Screens

A use case diagram visualizes the interaction of an external user with your system. So, you can say that in many situations [cases] that there is a need for an user interface, a screen. Not that strange that RUP connects the user interface designer to use cases. [see image below at the bottom]   UML Type: Artifact Something every diagram has in VSTS 2010 is the UML type ‘Artifact’. With this type we can attach physical pieces of information to or diagrams. For example in this diagram below, I defined an artifact which points to a class file. [don’t think it very useful to associate C# class files with use cases.. but as an example] Some nice functionality of this ‘artifact’ sh... [More]

Agile Testing with VSTS 2010 and TMap: Part 01-User stories

Previous post: Part 00: Agile Testing with VSTS 2010 and TMap … [current post] User stories breakdown... This post is about the work breakdown of user stories during the planning phase of an iteration. [image from the documentation about VSTS 2010 on MSDN, this page] During the planning phase of the project, also called iteration 0 [first blue piece], user stories are collected / brainstormed / defined /… in VSTS this information is collected in the new work item type ‘user story’ [image below].   During the planning of the iteration developers the team start to breakdown the user stories [which are selected for that iteration] in implementation tasks. With... [More]

Şarkı Sozleri