tutorial: create a custom work item in rational team concert

Tutorial: Create a custom work item in RationalTeam ConcertA hands-on example of using advanced customizations in aproject area

Skill Level: Intermediate

Seema Gupta ([email protected])Project Manager, Smart Deployment FactoryIBM

28 Jul 2011

You can customize or add entirely new work items in IBM® Rational Team Concert™project management tools to fit your team's needs. The team in this example usesagile development methods and the scrum process. Their project is highly dynamic,so they need to closely monitor potential risks. In following this article, you will createand test a fully functional, new type of work item called Risk, using the Rational TeamConcert Eclipse client, rather than the web client. Thereafter, because there is a anadditional type of work item added to the project called Risk, you can create andtrack more types of Risk work items using Rational Team Concert.

Prerequisite software

To follow this article, you need to have following software running and configuredproperly:

• IBM® Rational Team Concert™ version 3.0, which runs on the IBM®Rational® Jazz™ server

• Rational Team Concert 3.0, client for the Eclipse IDE

This software can be installed and configured according to instructions provided inthe "Extending Rational Team Concert" tutorial (see Resources for a link). After

Tutorial: Create a custom work item in Rational Team Concert Trademarks© Copyright IBM Corporation 2011 of 34

mailto:[email protected]

http://www.ibm.com/developerworks/ibm/trademarks/

http://www.ibm.com/legal/copytrade.shtml

completing that tutorial, you will have a local IBM® Rational® Jazz™ server up andrunning, named localrtcjazz.com. It can be accessed using this public URI:https://localrtcjazz.com:9443/ccm. The default administrator access on this serverhas been disabled, and a new admin user has been added as seemag, becausethese customizations are done by an administrator user.

After you have the server running, open the Rational Team Concert client for theEclipse IDE, and establish a connection to this local repository by using the option toCreate a new jazz repository connection. Provide the public URI,https://localrtcjazz.com:9443/ccm, and the admin user name andpassword for the repository.

Use case scenario

Consider the role of project lead of a team that is working in an agile developmentproject and using Rational Team Concert for project planning, tracking, andmanagement activities. Assume that the project environment is very dynamic andthere are too many risks, so there is a requirement to identify each risk carefully andtrack it until it ends. This can be achieved if the project team creates a custom workitem type called Risk and tracks it. This article shows how to do this in RationalTeam Concert 3.0.

Before you can create any customizations on work items, you need to have a projectarea created and named TestProject. For this tutorial, it has been createdalready by using the Scrum Process template.

Create a new Risk work item type

Any creation or customization of a work item requires the configuration of severaldifferent aspects of work items in Rational Team Concert: enumerations, work itemtype categories, types, attributes, workflows and workflow bindings, editorpresentations and editor presentation bindings. In any project area, all of theseentities are created independently and then bound together to create a fullyfunctional work item type.

The following steps are required to create a new Risk work item type that can becategorized as High Risk, Low Risk, or Medium Risk:

1. Define a new work item type with attributes.

a. Define a custom attribute for work item (which will hold theenumeration value)

developerWorks® ibm.com/developerWorks




2. Create a workflow.

a. Add all states of a Risk work item.

b. Add all actions applicable for a risk.

c. Add all applicable resolutions for a risk.

d. Associate appropriate actions with resolutions.

e. Identify transitions between various states of risk.

3. Create an editor presentation.

4. Bind the workflow and editor presentation with new work item type.

Define an enumeration called Risk Level

In Rational Team Concert any process configurations are done in ProcessConfiguration tab.

1. Select Process Configuration > Project Configuration > ProjectConfiguration Data > WorkItems > Enumerations.

Figure 1. Creating Enumerations in Rational Team Concert

ibm.com/developerWorks developerWorks®




2. Click Add to open the dialog window shown in Figure 2.

Figure 2. Providing ID and Name for an enumeration

3. Provide values as shown previously, and click OK. This will create a newenumeration called "Risk Level."

Figure 3. Risk Level enumeration





Because a risk can take a value of High Risk, Low Risk, or Medium Risk, the nextstep would be to associate these values with the previously created Risk Levelenumeration.

4. To add these literals in the Risk Level enumeration, click the Add button(see the previous screen, Figure 5), which will open the dialog windowshown in Figure 4.

Figure 4. Adding a high-risk enumeration literal in the Eclipse client





5. For each literal, select a name and (optionally) and icon.

Using icons as visual cues is a best practice and makes it much easier to pick outuseful information than using a screen full of text. If you don't see the icon that youwant, you can add more icons to the available icon list. Clicking OK will add HighRisk literal.

6. Add the other two literals, Low Risk and Medium Risk, in the same way.

Define a new work item type with attributes

After the enumeration is created, you need to create a new type of work item.

1. To add a work item, in the Project Area directory, select ProcessConfiguration > Project Configuration > Project Configuration Data >WorkItems > Types and Attributes.

Figure 5. Adding new types of work items





Initially, selecting the Types and Attributes tab will list all types of work items thatare available with the current process template of the Project Area, which is theScrum Project template in this case.

2. To add a new type to this list, click Add to open the Add Type dialogwindow shown in Figure 6, so you can provide a name and an ID for thenew type.

Figure 6. Providing Name, ID and Category for a work item





Each type of work item is associated with a category. You can choose a newcategory for the Risk work item type or reuse any existing default category.

3. For this example, create a new category for Risk.

4. Click OK.

5. On the resulting screen (see Figure 7), select a visual icon for this newtype Risk.

Figure 7. Initial screen after a Risk type is created





Scrolling down the screen will show other sections of a work item type, such asWorkFlow, Attributes, and so on. You will add a new attribute to Risk type first.

6. Scroll down to the Attributes panel.

7. Make sure that you check the check box labeled Show only customattributes to avoid viewing all default attributes required for functionalityof the tool. Initially, there will not be any custom attribute for new Riskwork item type.

Define a custom attribute that can hold the enumeration value

You will define a new custom attribute that can hold values from enumeration risklevel and name it Risk Level.

1. To add this custom attribute, click Add on the right side of Attributessection to open the dialog window shown in Figure 8.

Figure 8. Adding custom attributes for a work item





2. Besides Name and ID, for Type, select the Risk Level enumeration,which you already created.

3. Click OK, and then make sure that the attributes section of the Risk workitem type reflects this new custom attribute.

Create a workflow for the newly created work item type

A workflow is a definition of the states, actions, resolutions, and transitions thatrepresent the life cycle of any work item type. Hence, any work item must have aworkflow. Based on stakeholder discussions, the following workflow illustrated inFigure 9 has been identified for the Risk work item type.

Figure 9. Workflow for a Risk type

1. To start creating a workflow for a work item in Rational Team Concert,open the project area and select Process Configuration > ProjectConfiguration > Configuration Data > WorkItems > Workflows (seeFigure 5).

2. On the right side of the Workflows pane, click Add to open a new dialogwindow, so you can provide an ID and Name for the workflow that you aredefining:

• ID: RiskWorkFlow

• Name: Risk WorkFlow





3. Click OK, and a new workflow with the name Risk WorkFlow will becreated.

The workflow created in this state acts as a container that will be populated with fivedata elements for Risk, as mentioned in the descriptions of the steps that follow:

1. Add all states of a Risk work item.

2. Add all actions applicable for a risk.

3. Add all applicable resolutions for a risk.

4. Associate appropriate actions with resolutions.

5. Identify transitions between various states of risk.

In the following subsections, you will populate the Risk WorkFlow with previous data.

Add all states of a Risk work item

1. To add states in a workflow, go to Workflows tab and select the RiskWorkflow that you created.

As the state diagram in Figure 9 shows, a Risk can be in one of four states:Identified, Analyzing, Blocking, and Closed. The workflow will have varioussections such as States, Actions, and Transitions.

2. Scroll down to States section and click Add to open the Add State dialogwindow shown in Figure 10 (this screen was captured with differentvalues specified for the Identified state).

Besides the Name, Icon, and Description fields, there are two more parametershere: Group and Show Resolution.

Figure 10. Adding a new state to the Risk workflow





Any state in Rational Team Concert can be categorized into one of three standardgroups:

• Open

• In Progress

• Closed

Because a Risk in the Identified state is an open work item, the Open group hasbeen chosen.

3. The Show Resolution check box needs to be checked only if it tags thework item as Closed with a proper resolution. In Figure 10, this check boxis unchecked, because the Identified state doesn't tag the work item as





Closed.

4. Click OK to create the identified state.

You can create Analyzing, Blocking and Closed states in a similar way. The onlydifference is that, while creating a Closed state, the Show Resolution check boxneeds to be checked. After all the states are created, the States section will looksomething like Figure 11.

Figure 11. States of the Risk work item in the Risk workflow

Add all actions applicable for a risk

In this step, all actions applicable on a Risk will be added. In the state diagram(Figure 9), arrows represent actions and eclipses represent states. As an example,initial action for any Risk is Open, which will create a Risk in Identified state.

1. To add this action, scroll to Actions section of Risk Workflow editor andclick on Add to open a dialog window to add details about actions, asFigure 12 shows.

Figure 12. Adding Open Action in Risk Workflow





By this time, the information in the Name, Icon, and Description fields will startlooking quite familiar. Besides these regular attributes, each action needs to providean additional parameter for Target State. Because the Open action leads to theIdentified state, the Target State in the previous diagram is selected as Identified.

2. Click OK to create the Open action.

3. Add all other actions for a Risk work item in a similar fashion.

After all of the actions have been added, the Actions section of the Risk workflow willlook like Figure 13.

Figure 13. Actions section of workflow after adding all actions for Risk





The workflow for a work item also needs to provide the primary actions such asStart action, Resolve action, and Reopen action. These are the actions for theRisk work item:

• Start action = Open

• Resolve Action = Close

• Reopen action = Reopen

You can select these values in the workflow.

Figure 14. Associating the Risk workflow with Start, Resolve, and Reopenactions

Add all applicable resolutions for a risk

In this step, all possible resolutions for a Risk work item will be added in the Riskworkflow. Assume that, based on stakeholders' discussions, a risk can be handled inonly three ways: mitigating, containing, or declaring it invalid. So you will add threeresolutions: Mitigated, Contained, and Invalid.

1. Scroll down to the Resolutions section and click Add to open the dialogwindow shown in Figure 15.

Figure 15. Add Resolution dialog window in the Risk workflow





Note:The screen capture provided here reflects values for Contained resolution.

2. Click OK to create the Contained resolution.

3. Add two other resolutions, Mitigated and Invalid, in the same way.

After you add all of the resolutions, the Resolutions section of the workflow, it willlook like Figure 16.

Figure 16. Resolutions section of the Risk workflow





Associate appropriate actions with resolutions

After you have added all of the resolutions, it's time to revisit actions in the workflowand associate resolutions with actions that can lead to resolutions of a Risk. In thecurrent scenario, only the Close action can resolve the Risk.

1. To associate this action with Resolutions, select Close and select thecheck boxes for all resolutions (Contained, Mitigated, and Invalid). Theactions pane of the Risk workflow will then display what Figure 17 shows.

Figure 17. Actions in the Risk workflow after adding resolutions to actions

The end user is presented these resolutions in the same order as they appear in theworkflow. You can move items up or down with the buttons toward the right side ofActions pane.

Identify transitions between various states of a Risk item

In this step, you need to identify the transitions between various states of a workitem. If you do not identify this, the Transitions pane of the Risk workflow will appearas the matrix in Figure 18 shows.

Figure 18. Initial Transitions Section in the Risk workflow





The matrix for various states has already been created. The transitions for variousstages need to be identified and populated in the matrix. Looking at the statediagram closely, the following observations can be made:

• An Identified risk can get into only an Analyzing state, and the action withwhich the state can change is Assign. It cannot directly go to any otherstate.

• A risk in the Analyzing state can move into the Blocking state or Closedstate, depending on whether an Escalate action or Close action has beentaken.

• A risk in Blocking state can get into the Analyzing or Closed state,depending on whether a Revisit or Close action has been taken.

• A risk in Closed state can get into the Analyzing state if a Reopen actionhas been taken.

Based on these observations, you can provide the transitions shown in Figure 19:

• Identified to Analyzing with an Assign action

• Analyzing to Blocking with an Escalate action and Analyzing to Closedwith close action

• Blocking to Analyzing with a Revisit action and from Blocking to Closedwith close action

• Closed to Analyzing with a Reopen action

Figure 19. Final Transitions section in the Risk workflow





With the creation of transitions, you have finished creating the workflow for the Riskwork item.

Create an editor presentation for the new work item type

An editor presentation acts as the form to present a work item to users. In currentversions of Rational Team Concert, a work item can be displayed four differentways:

• Work Item Editor, the presentation used in the Eclipse client and the webclient when displaying a work item in the Editor view

• Inline Work Item Editor, used in web client to display work item details in aPlan view

• Lightweight Work Item Creation dialog, used in the web client whencreating work items

• Plan Editor Preview, displayed as a pop-up window in the Eclipse clientwhen the user moves the cursor over a work item in the Plan Editor view

Important:A work item can be viewed in any type of presentation, so all four editorpresentations need to be created for any work item type. All of the editorpresentations are created in same way. This article covers only creation of the WorkItem editor presentation for a Risk, but you need to create the three other editorpresentations before using the new work item type in a project area.

Rational Team Concert provides a default editor presentation that includes most ofthe fields, tabs, and so forth that are required to present any work item. The defaultlayout can be changed by adding a few custom attributes.

1. To start adding or editing the Risk work item editor presentation, go backto Process Configuration > Project Configuration > ProjectConfiguration Data > WorkItems > Editor Presentations, as shown inFigure 20.





2. Look at combination box with title of Choose the editor presentation toedit. By default, the value will be com.ibm.team.workitem.editor.default.Retain the default value, and click Duplicate.

3. A dialog window will open for you to provide the ID for the duplicatededitor presentation. Give it a suitable name, such asRiskWorkitemEditorPresentation, and click OK.

Figure 20 shows the RiskWorkitemEditorPresentation.

Figure 20. Duplicated Risk editor presentation based on the default one

A presentation or view is divided into various tabs, sections, and presentations. TheHeader, Overview, Links, Approvals, and so on form the tabs, and each tab hasmore parts. For example, the Overview tab contains all details of a work item, andlinks refer to links for a work item. Depending on where you want to change theview, the editor presentation needs to be modified. For this example, you are addingonly one attribute in Details for the work item, and it can hold the value of Risk Level.

Details are part of the Overview tab, so you start these modifications there.

Important:Shared content should not be modified directly in an editor presentation, becausethis would be shared between multiple editor presentations.

The Overview tab in Risk Work Item editor presentation has a "content shared" tag





against it, and this should be duplicated before making any modifications.

4. Select Overview, and click Duplicate.

5. In the dialog window that opens, provide an appropriate name (Overviewin this case), and click OK.

This will create an additional Overview tab that will not have a[content shared]notation. After the Overview tab is created, it's time to modify the Details sections toshow the new Risk Level custom attribute in the Work Item editor presentation.Again, the Details section is shown with a [content shared] notation; therefore, itneeds to be duplicated first.

6. Select Details and click Duplicate once again.

7. When you are prompted for an ID for duplicated section, provide anappropriate name and click OK.

At this stage, there will be two Overview tabs and two Details sections, one with the[content shared] notation and one without it, as shown in Figure 21.

Figure 21. Risk Work Item editor presentation after duplicating Overview andDetails

Because you have Overview tabs and Details sections created specifically for theRisk editor presentation, you don't need the shared Overview tab and Details section





anymore.

8. To remove those sections or particular elements of the editorpresentation, select the appropriate element (Overview [shared content]and Details [shared content]), and click Remove.

After you remove the shared Overview tab and Details, notice that you have onlyone Overview and Details section, without any shared content in theRiskWorkitemEditorPresentation view.

The next step is to modify the presentation for the custom attribute that you want toshow in the Risk Work Item Editor: Risk Level.

9. Expand the Details section by clicking on the plus sign + of the Overviewtab, and then click Add Presentation.

This will open a dialog window to provide values for presentation field. Thepresentation can be attribute-based or non-attribute-based.

10. Since you are adding the presentation field for a custom attribute of aRisk work item, select Attribute-based presentation.

Figure 22. Provide values for an attribute-based presentation





The Risk Level has been chosen as the attribute, because the presentation is beingadded for the Risk Level attribute of the Risk work item type.

11. Choose Kind as an Enumeration, because Risk Level is an enumerationtype.

12. A label is required for visual identification of the presentation field.





13. Click OK.

There will now be a new presentation created for Risk Level in the Details section.You can change the position of this presentation by clicking the Move Up or MoveDown button.

Figure 23. Risk Level presentation added to the presentation

With this, you have finished creating the Work Item Editor for the Risk work item.

Reminder:Remember to add the other three types of editor presentations to be able to view thework item properly in all views.

Bind the workflow and editor presentation with the Risk work item

Until now, the workflow and editor presentations that you created exist asindependent identities, without any link to the Risk work item type created earlier.

1. To link these entities, go back to Process Configuration > ProjectConfiguration > Configuration Data > WorkItems > Types andAttributes, and select the newly created type, Risk.





Any work item in this place will have selection boxes to choose its various attributes,such as Work Item Editor, Inline Work Item Editor, Lightweight Work Item CreationDialog, Plan Editor Preview, Workflow, and so forth.

2. To select the editor presentations and workflow that you created asvalues of the Work Item editor presentation and workflow for the Risktype, choose the values shown in following two screen captures.

a. (Figure 24) In the Project Area screen, under the Types andAttributes view, for Work Item Types, select Risk from the list.

b. For the Work Item Editor field, selectRiskWorkItemEditorPresentation from the drop-down menu.

c. (Figure 25) In the next view, under Workflow, select RiskWorkflow from the drop-down menu.

Figure 24. Binding the Work Item Editor Presentation with the Risk type ofwork item

Figure 25. Binding the workflow with the Risk type





Reminder:Remember to bind other three types of editor presentations (inline work item editor,Lightweight Workitem Creation dialog and Plan Edior Preview) to be able to view thework item properly in all views.

3. Choose appropriate values for other three types of editor presentations,using the names that you gave to those.

You have now created a fully functional type of work item called "Risk."

Test the new Risk work item

1. In the Team Artifacts view, to test the new work item type that you havecreated, open the TestProject project, and select Create Work Item.

Figure 26 shows the resulting Create Work Item screen.

Figure 26. Creating a new work item in Rational Team Concert





2. Notice that there is now a type of work item called Risk. Select it, andthen click Finish.

This will create a new Risk work item. Notice the highlighted parts in the screencapture (Figure 27): Low Risk and Uninitiated [inactive]. A Risk Level attribute isdisplayed in the third row, with a default value of Low Risk, and the initial state ofRisk is Uninitialized.

Figure 27. New risk created





As you recall from the workflow, a risk should move into the Identified state as soonas it is opened. Rational Team Concert treats the Risk as Opened only when it issaved to the project.

3. Save this Risk, and the state will change to Identified.

Figure 28. Risk now shown in the Identified state





To test the workflow of this Risk work item, take specific actions.

4. As an example, select Assign for this new Risk.

Figure 29. Performing an Assign action on a risk

As soon as Assign action is applied, the state of risk is changed to Analyzing.

Figure 30. Risk in Analyzing state after performing the Assign action





At any point, you can choose to perform actions, as long as they are feasible fromcurrent state of a risk. Based on the action taken, the state of the Risk work item willkeep changing. For example, an Escalate action will lead to a Blocking state, asshown in Figure 31.

Figure 31. Risk in Blocking state after an Escalate action

You can also test that Resolutions being shown when a Close action is beingperformed and choose different resolutions. Using the second highlighted drop-downmenu, to the right of the state (status) field, you can choose various resolutions.They are in the same order as you defined them in the workflow. When theresolution is selected and saved to the Project Area, the resolution can no longer beedited.

Figure 32. Performing a Close action on a Risk work item

Larger view of Figure 32.

Summary



figure_32.html



Rational Team Concert provides extensive process configuration options to meetrequirements of almost every project. This article covered one of thosecustomizations for work items in Rational Team Concert. As a part of thiscustomization, a new type of work item was created for risks, along with its variousaspects, including enumerations, custom attributes workflow, and so forth. Therewere details about various parts of the workflow, focusing on states, transitions,resolutions, and actions. After all of the independent identities were created andlinked, the newly created work item type was tested. Team members can now createcustom work items for different risks, based on that "umbrella type" of Risk workitem.





Resources

Learn

• Find Rational Team Concert articles and links to many other resources on theIBM developerWorks page. You can also watch the Using Rational TeamConcert in a globally distributed team webcast or a demonstration of theDashboards and reports, or listen to the podcast about IBM Rational TeamConcert and Jazz.

• Follow the Extending Rational Team Concert tutorial to install and configureRational Team Concert and the Eclipse client.

• Visit the Rational software area on developerWorks for technical resources andbest practices for Rational Software Delivery Platform products.

• Stay current with developerWorks technical events and webcasts focusedon a variety of IBM products and IT industry topics.

• Attend a free developerWorks Live! briefing to get up-to-speed quickly onIBM products and tools, as well as IT industry trends.

• Watch developerWorks on-demand demos, ranging from productinstallation and setup demos for beginners to advanced functionality forexperienced developers.

• Improve your skills. Check the Rational training and certification catalog, whichincludes many types of courses on a wide range of topics. You can take someof them anywhere, any time, and many of the "Getting Started" ones are free.

Get products and technologies

• Rational Team Concert trial downloads (free):

• Enterprise Edition

• Express Edition

• Standard Edition

• Evaluate IBM software in the way that suits you best: Download it for a trial, tryit online, use it in a cloud environment, or spend a few hours in the SOASandbox learning how to implement service-oriented architecture efficiently.

Discuss

• Join the Rational Team Concert discussions or ask questions in the Jazz.netforums.

• Share your knowledge and help others who use Rational software by writing a



http://www.ibm.com/developerworks/rational/products/rtc/

http://jazz.net/blog/index.php/2009/01/06/webcast-using-rational-team-concert-in-a-globally-distribute-team/

http://jazz.net/blog/index.php/2009/01/06/webcast-using-rational-team-concert-in-a-globally-distribute-team/

http://www.ibm.com/developerworks/offers/lp/demos/summary/r-rtcdashboard.html

http://www.ibm.com/developerworks/podcast/spotlight/st-111907txt.html

http://www.ibm.com/developerworks/podcast/spotlight/st-111907txt.html

https://www.ibm.com/developerworks/mydeveloperworks/blogs/extendingrtc/entry/preparing_for_extending_1of3?lang=en_us

http://www.ibm.com/developerworks/rational

http://www.ibm.com/developerworks/offers/techbriefings/events.html

http://www.ibm.com/developerworks/offers/techbriefings/

http://www.ibm.com/developerworks/offers/lp/demos/

http://www.ibm.com/software/rational/education/

http://www.ibm.com/developerworks/downloads/r/teamconcert/learn.html

http://www.ibm.com/developerworks/downloads/r/teamc/learn.html

http://www.ibm.com/developerworks/downloads/r/rtc/learn.html

http://www.ibm.com/developerworks/downloads/

http://www.ibm.com/developerworks/downloads/soasandbox/index.html

http://www.ibm.com/developerworks/downloads/soasandbox/index.html

http://jazz.net/forums/index.php?c=2

http://jazz.net/forums/index.php?c=2



developerWorks article. You'll get worldwide exposure, RSS syndication, abyline and a bio, and the benefit of professional editing and production on thedeveloperWorks Rational website. Find out what makes a gooddeveloperWorks article and how to proceed.

• Follow Rational software on Facebook and Twitter (@ibmrational), and add yourcomments and requests.

• Ask and answer questions and increase your expertise when you get involvedin the Rational forums, cafés, and wikis.

• Connect with others who share your interests by joining the developerWorkscommunity and responding to the developer-driven blogs.

About the author

Seema GuptaSeema Gupta is a project manager at IBM Software Labs in Bangalore,India. She has undergone several trainings on Rational Team Concertand uses it extensively for all projects.



https://www.ibm.com/developerworks/secure/myideas.jsp?start=true&domain=

http://www.ibm.com/developerworks/rational/library/what-makes-a-good-developerWorks-article/index.html

http://www.ibm.com/developerworks/rational/library/what-makes-a-good-developerWorks-article/index.html

http://www.facebook.com/IBMRational

http://twitter.com/#search?q=ibmrational

http://www.ibm.com/developerworks/forums/dw_rforums.jspa

http://www.ibm.com/developerworks/rational/community/cafe

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en_US#/wiki/Rational%20Wiki%20Central/page/Rational%20Wiki

http://www.ibm.com/developerworks/community/

http://www.ibm.com/developerworks/community/

https://www.ibm.com/developerworks/mydeveloperworks/blogs/?lang=en



tutorial: create a custom work item in rational team concert

Technology

risk levelin rational

custom work item

project team

new type of work item

new work item type

low risk

medium risk

types of risk work items