Articles, Blog

Tracking and Planning with Rational Team Concert

December 2, 2019


Hi, I’m Jean-Michel from IBM Rational. In this video we’re going to show you some cool features
that are part of the tracking planning support in Rational Team Concert. Our goal is to focus on the collaboration transparency
and the full lifecycle traceability that you can get with Rational Team Concert. to make this as concrete as possible let’s look at a couple of scenarios we’re going to cover.
We’re going to look at status in the dashboard we’re going to release and iteration planning
we’re going to customize work items to fit your needs and we’re going to show how you can use the web to modify files directly. Now Rational Team Concert is available for different clients
for visual studio, for eclipse and for the command line but for this demo, we’re going to focus on the web UI. now all practices can be available in one
place. In this call center example they have an overview page which provides simple
access to the download files that are actually stored in Rational Team Concert. In addition everybody in rational team concert has
a role and these rolls are used to customize things like what events you’re
going to get what permissions you have and what approvals are needed in addition because Rational Team Concert has all
the artifacts in one place we can provide very useful transparency along
all the artifacts so we can quickly get a glance of builts that have succeeded change sets that need review, work items that have been
changed, approvals that are required from you messages directly attributed to you as well so the dashboard can be used to show both the transparency
but the value here is the ability to show transparency across all of the different roles. so let’s switch over to our planning hat and look at a dashboard that is focused on planning now dashboards are customizable and in this case the planning team has decided to highlight the current plans that are in progress two stories that are in being blocked and
that haven’t started yet and some burn-down information And this of course is completely customizable and we’ve got a set of viewlets and dashboards that can be added to your dashboard
to fit your needs in addition the viewlets we’ve also provided some in place editing and tool tip support so you don’t have to
switch context when you want to look at more details of an artifact now let’s focus on some of the planning capabilities
and editing plans So Rational Team Concert includes planning function that’s great for both scrum teams and agile teams
but it’s also very useful for teams who have more a waterfall
approach the main goal here is to get rid of your spreadsheets and bring them into a tool in which your team
can collaborator around find out events and actually worked on together so in this case we have release plan and plans can be seen in different views you can
have backlogs, ranked lists where you can see by team in this case for going to focus on decomposition by sprint so let’s show how easy it is to go add and edit
the plan in place in the web ui. so we’re going to add a story we’re not going to add it to a sprint
yet we’re just going to put it in our backlog
for the iteration sorry for the release usually when you add stories your going to add subtasks
and you do some decomposition Now our team uses this in all of our meetings
when we talk about planning or we have some discussion about what we’re going to do
we will open up the plan on the web and and start doing some
decomposition Now releasedplans are one way of looking
at your you’re planning there’s also a set of related plans that are
interesting so you can go to the product backlog which shows your ranked list of items that you haven’t really asigned to a release yet
so it let’s you triage and manage your backlog and actually go go directly and from your backlogs you can have reviews
and add things or remove things from different releases as you like now you can switch back to your release plans and we’re just going to do a quick refresh
and we’re goign to triage these items that are have been newly added to our backlog Now directly in the web ui, we’ve got drag and drop support as well, so you can drag
and drop enhancements, defects, features, stories
from of different iterations from your release backlog into your sprints
and it lets you very easily do load balancing and do your planning without having to do some copy
and edits in some spreadsheets. What’s interesting as well is that team members
are actually going to see this planning and you don’t have to go and send an e mail explaining exactly
what was happening you can do the planning directly from the web. So in
this case we’re going to go into what we call
iteration planning. In the release planning phase we worry more about load balancing across different iterations now in this case you get to see people’s pictures
which is we’re in a particular iteration and we want go do some load balancing across
developers — so again drag and drop is supported and you can see different people with different
load balances and you can also two different views. And in
this case we have a traditional scrum taskboard meeting where you can do your stand up meetings
looking at your task boards. now all this planning is really based on a
common theme which is we’ve go access work items work items are the elements that you actually plan now some of the cool nifty support of work items is the support to do advanced queries and to customize your work items so let’s look at an advanced query first so queries again can be shared — everything in
rational team concert can be shared within the team level, within developers, and
can be collaborated on. so in this example, one of the cool things — one of the friction
points betwen teams is dependencies. so I’m going to write simple query which is basically
going to use some of the tracibility links that we have in Rational Team Concert
so what I want to do is look at all the open unresolved work items that have a dependency so I got two work items that are being blocked and blocked work items are important because it means
that we are waiting on another team to do work for
us and that level of transparency is really interesting now most of the work items are customizable
which means that out of the box we have support for different processes like scrum and the different work items types and the different work flows are actually
built into the configuration of your project. and this can be customized so again, one of the cool features is customization and going back to some of the roles we had Knowing the roles, the whole permission model for
Rational Team Concert is hooked up to roles as well so you can in this example decide you know is it a product owner, a scrum master
or release engineer that can trigger certain workflows on
certain work items so one fo the last things I wanted to highlight was from an actual user on a team, what can they do so what we’re going to do
now is fixing a bug in our website directly from the web UI and edit the file and have it deployed
to our website. so we’re still in the Web UI and we have function in Rational Team Concert that
that lets you click on links and I can have access to the source control files so in this
case we have our web site as you can see it’s been stored in Rational Team concert and we’ve got our
index.html here and we’re actually going to go and in-place we’re going to edit the index.html because there is a little
typo we want to add something to it.
So that is easy enough to do so let’s just go make a change to this file well we’re going to go ahead and just add
a check in comment were also going to add a work item to this. Again Tracability is really
important so tracing back what changes have been made and for what reason people are going to get an events about this and they can come quickly see what people are up to so in this case we’re just going to say
that we have updated the header and save so now this website html has been saved
and is part of Rational Team Concert. now one of the cool futures as well in Rational
Team Concert is support for automation and builds so we have a simple build here that’s called staging web deploy and this build basically takes a code the web site that is in Rational Team Concert
and puts it on disk some where. so i haven’t run a build yet. so I’m going to go
look at my web site and you can see here that I’ve got Call Center
a very simple web site page and what i’m going to go do is kickoff a build and I’m going to submit it directly from the web it’s going to kick off the build and it’s going to fetch the files they’ve been stored RTC that’s going to put them on the disk and then
our website should be updated there we go so you’ve seen a pretty end to end scenario of opening a work item, we’ve traversed
directly to the file we’ve seen the reasons and we’re going to finish
up here by looking at the fact that you can see tracablity along builds, you can see change sets and you can see who subscribed to this, all
in one place we’re going to complete this task and now our team has tracabilty along
the whole life cycle. again this was the tip of the iceberg.
Please come join us on jazz.net download and give us some feedback. Thanks.

You Might Also Like

6 Comments

  • Reply jonathan valdez September 5, 2011 at 3:51 pm

    Me gusta, lo maximo

  • Reply philippeback September 10, 2012 at 8:02 am

    Nice to see the demo done on a Mac box 🙂

  • Reply Chirag Deshpande June 25, 2014 at 4:15 am

    Can you please tell which version are you using

  • Reply sumit sinha September 24, 2015 at 9:29 pm

    too fast…though nice one!

  • Reply Teo Velicu December 7, 2016 at 1:55 am

    excelent integration in a end to end real dev scenario. much better than jira, conflunce, jenkins, team city and intelli j idea collection….

  • Reply R B April 17, 2018 at 11:51 am

    How can I Show the History for each Work Item with a Query?

  • Leave a Reply