Collaborative Application Lifecycle Management Solutions from IBM Rational. Presentations

Transcription

1 Collaborative Application Lifecycle Management Solutions from IBM Rational Presentations

2 An IBM Proof of Technology PoT.Rational _rev Copyright IBM Corporation, 2009, 2011 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Collaborative Application Lifecycle Management Solutions from IBM Rational An IBM Proof of Technology 2010 IBM Corporation Welcome to the Technical Exploration Center Introductions Access restrictions Restrooms Emergency exits Smoking policy Breakfast/Lunch/Snacks location and times Special meal requirements? 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 2

4 Introductions Please introduce yourself Name and organization Current integration technologies or tools in use What do you want out of this Exploration session? 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 3 Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 4

5 Objectives Explore how the IBM Rational tools support collaborative application lifecycle management by: Enabling teams to collaborate in real time in the context of the work they are doing, especially in globally diverse environments Enabling projects to be managed more effectively by providing visibility into accurate project health information drawn directly from actual work Automating traceability and auditability by managing artifacts and their interrelationships across the lifecycle, empowering teams to deliver more value Provide a hands-on experience using IBM Rational Requirements Composer, IBM Rational Team Concert and Rational Quality Manager to automate the software delivery process 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 5 Introduction to Collaborative Application Lifecycle Management (C/ALM) An IBM Proof of Technology 2010 IBM Corporation

6 Traditional Application Lifecycle Management (ALM) solutions result in islands of people, process and information Little to no project visibility Data locked in proprietary application programming interfaces (APIs) Poor process and workflow integration High maintenance and administration costs Persistent functional, geographic and organizational silos 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 7 A platform approach to ALM can break down organizational, functional and geographic barriers Real-time, transparent access to project data, risks and progress Third-party products Open source solutions Product A Product B Process Workflow Product C Product D HTTP/REST Shared Platform Services Integrated, loosely coupled Logic, User Interfaces Data Models, Workflow Administration 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 8

7 IBM Rational Jazz-based Collaborative ALM platform Transforms software and systems delivery Provides: Collaboration Automation Reporting c A scalable, extensible team collaboration platform Role-based support for entire project team End-to-end, asset traceability and enforceable process workflows A way to make software asset reuse practical with integrated asset management IBM Rational Jazz is a project and software delivery platform for transforming how people work together to deliver greater value and performance from software investments. Predictable software release management and measurable improvement through full lifecycle reporting 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 9 Collaborative ALM integrations For this Proof of Technology (POT) we are trying out the integrations between Rational Requirements Composer Rational Team Concert Rational Quality Manager All of which are built on the Jazz Foundation C/ALM builds on the Jazz Foundation integration support Common User Interface elements Collaboration in context with cross repository linking and queries Dashboards supporting transparency of C/ALM information 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 10

8 The foundation of Collaborative ALM Rational Requirements Composer Business expert collaboration Elicit, capture, elaborate, discuss and review requirements Rational Team Concert Core team collaboration "Think and work" in unison and provide real-time project heath Rational Quality Manager Quality team collaboration Coordinate quality assurance plans, processes and resources Changes; notification Association Analyst REST API Requirement linked to work item Tester finds defects, generates work item REST API Tester Requirements Management Defects closed against requirements Defect status Quality Management REST API Change and Configuration Management Architect Developer 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 11 Collaboration fosters business alignment and high quality Requirement links foster clarity Analyst Rational Requirements Composer Developer Rational Team Concert Developers link to requirements from work-items Tester Rational Quality Manager Testers link to requirements from test plans and test cases Analysts communicate requirements with links to development and test plans 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 12

9 Collaboration fosters business alignment and high quality Defect links speed time to resolution Analyst Rational Requirements Composer Developer Rational Team Concert Tester Rational Quality Manager Test Execution Results link to defects Defects can link to requirements Defects link to Test Execution results 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 13 Practices Practices In addition to tools to enable collaboration, C/ALM also includes a set of best practices to guide practitioners and teams IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 14

10 Rational Requirements Composer, Rational Team Concert and Rational Quality Manager integrations Rational Requirements Composer user capabilities: Link requirements sets to Rational Quality Manager test plans Create/link requirement artifacts to Rational Quality Manager test cases Create/link requirement artifacts to Rational Team Concert plan items Create C/ALM mash-up dashboards containing viewlets from Rational Team Concert and Rational Quality Manager Rational Team Concert user capabilities: Link plan items to Rational Requirements Composer requirement artifacts Link plan items to Rational Quality Manager test cases Navigate links from defects to test execution results to browse detailed test data Create C/ALM mash-up dashboards containing viewlets from Rational Requirements Composer and Rational Quality Manager C/ALM query examples: Defects blocking test, Plan items without associated requirements, Plan items without associated test cases Rational Quality Manager user capabilities: Link test plans to rational requirements composer requirements sets Link test cases to Rational Requirements Composer requirements and Rational Team Concert plan items Create/link test execution results to Rational Team Concert defects Create C/ALM mash-up dashboards containing viewlets from Rational Requirements Composer and Rational Team Concert C/ALM query examples: Tests blocked by defects, Defects blocking test, Plan items without associated test cases Administrators can: Establish Rational Requirements Composer, Rational Team Concert and Rational Quality Manager repositories as friends Link development and testing project areas 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 15 Jazz is a platform for transforming software delivery Jazz is Rational Offerings Third-party Offerings c Business Partner Offerings Our vision of the future of systems and software delivery Business Product Collaborative Planning & & Project Lifecycle Compliance Your Alignment Management Management & Security Engineering existing & Software 3 Future capabilities rd -Party Tools Jazz IBM Capabilities Capabilities Best Practice Processes Administration: Collaboration Users, projects, Presentation: Storage process Mashups Discovery Query Rational collaborative ALM solutions transform how people work together to deliver greater value and performance from their software investments. The technology foundation of our collaborative ALM solution An integration architecture enabling mashups and non- Jazz products to participate A community at Jazz.net where Jazz products are built An evolution of our portfolio over time 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 16

11 Open Services for Lifecycle Collaboration Simplifying collaboration across the software delivery lifecycle Open Services for Lifecycle Collaboration Open interfaces. Open possibilities. An industry initiative for making it easier to use software delivery tools in combination. Barriers to sharing resources across the software lifecycle Multiple vendors, open source projects, and inhouse tools Private vocabularies, formats and stores Entanglement of tools and data The Open Services initiative is Building a community of software vendors, open source projects, integrators, and corporate IT teams, operating at open-services.net Creating public specifications of resources and services for sharing the things that software teams rely on, like change requests, test cases, defects, requirements and user stories Delivering loosely coupled resource formats and services with just enough standardization 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 17 Creating a higher-fidelity connection to our customers Suppose we did our development out on the Internet? A transparent software delivery laboratory where you can... Communicate with the development team Track the progress of builds and milestones Get the latest product trials and betas Join developers and product managers in discussion groups Submit defect and enhancement requests 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 18

12 Learn more on Jazz.net 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 20

13 Gartner Marketscope on Application Lifecycle Management IBM Rational Positioned as a Clear Leader in this Expanding Segment IBM is one of the few vendors with credible offerings in almost all the requirements of ALM IBM Rational is one of the first vendors to tell a story about integrating across the lifecycle Jazz is a solid architectural foundation for further innovation We rate IBM as a Strong Positive because of its current market strengths and breadth of portfolio 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 21 What analysts are saying... Liz Barnett, Ez-Insight: "With the Jazz project, Rational has developed breakthrough technology and is poised to set the standard for collaborative ALM... Given the current business climate of deliver more with less much sooner, organizations have no choice but to rethink the ways that they deliver software solutions. The Jazz project will help teams achieve that goal." Paul Herzlich, Ovum: "IBM has taken the opportunity to exploit the Jazz platform s power inventively. Its living test plan is a masterpiece of applying new technology to a familiar problem What is being delivered will demonstrate convincingly that IBM is raising the standard for a test management product." Julie Craig, EMA: "Rational s differentiators are difficult for competitors to equal, and the new Jazz platform foundation may well turn out to be one of the best investments the Rational team has made. Simon Jacobson, AMR: Frankly I wish folks who sold quality management solutions took this approach. Most of the folks I speak to talk about the life cycle, but they are selling you a mass transit system, but only really provide the train station IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 22

14 2010 IBM Corporation Collaborative Application Lifecycle Management Solutions from IBM Rational 23

15 Lab Overview An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Lab Overview 25

16 Scenario for Proof of Technology (PoT) Labs You will play the role of various members on a project (called Squawk) as they work through the definition, prioritization, implementation, testing and fixing of a new requirement: Bob: The product owner Scott: The Scrum master Deb: A developer Tanuj: The test lead Marco: The development lead The project follows the Scrum methodology. You will be using Rational Requirements Composer, Rational Team Concert and Rational Quality Manager as the project s collaborative development environment IBM Corporation Lab Overview 26 Quick Scrum Overview Scrum is an agile process for software development. (Often spelled SCRUM, although not an acronym.) Scrum roles: Scrum Master: Individual who maintains the processes (essentially a project manager). Responsible for removing impediments to team progress. Product Owner: Represents the stakeholders Team: Cross-functional group of people who do the work Scrum concepts: Story: A brief description of a user need. Each story has a relative priority and complexity. Product backlog: A prioritized set of high-level requirements of work, usually described in stories. Sprint: A two-to-four week period in which the team creates a potentially shipping product. A Scrum project consists of several sprints. Sprint planning meeting: A meeting to determine which backlog items go into a sprint. Scrum: A short daily meeting where each team member shares what they accomplished yesterday, what they will work on today and what, if anything is blocking their progress IBM Corporation Lab Overview 27

17 Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott Marco Deb Tanuj (SCRUM Master) (Development Lead) (Developer) (Test Lead) Module 1 Update the Product Backlog Describe highest priority features Define sprint goal Module 2 Plan the Sprint Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint 2010 IBM Corporation Module 3 Manage the Sprint Check team alignment Develop surfer squawker Monitor integration build Align test sprint plan Create test scripts and test execution records Module 4 Implement the Sprint Plan Monitor build status Execute test and submit defect Module 5 Respond to a Test Failure Triage Fix defect and deliver defects change Confirm defect is fixed the sprint Module 6 Monitor the Sprint Lab Overview 28 Rational Solution Components for C/ALM Rational Team Concert Innovation Through Collaboration Unify by thinking & working in unison with real-time project heath Rational Quality Manager Collaborative Business-Driven Quality Coordinate quality assurance plans, processes and resources Rational Requirements Composer Business Expert Collaboration Elicit, capture, elaborate, discuss and review requirements Rational Team Concert offering offering Rational Quality Manager Best Practice Processes offering Rational Requirements Composer IBM Business Partner Jazz Offerings Search and Query Security Dashboards Team awareness Events notification collaboration IBM Rational JAZZ TEAM SERVER Open Lifecycle Service Integrations ClearQuest Powered by ClearCase Build Forge RequisitePro Asset Manager 2010 IBM Corporation Lab Overview 29

18 Rational Requirements Composer: A closer look Rich Authoring Environment Web Review and Approval Use Cases Rich Text Requirements Wiki style interface Categorize / Tag Comment Review / Approve Glossaries UI Sketching and Storyboarding Process Sketching Collaboration Server Share work instantly Users / teams / authorizations Linking between all artifacts Versioning 2010 IBM Corporation Lab Overview 30 Rational Team Concert: A closer look Iteration Planning Integrated iteration planning and execution Task estimation linked to key milestones Out of the box agile process templates Project Transparency Customizable Web based dashboards Real time metrics and reports Project milestone tracking and status SCM Integrated stream management Component level baselines Server-based sandboxes Parallel development Rational ClearCase connector Work Items Defects, enhancements and conversations View and share query results Support for approvals and discussions Query editor interface Rational ClearQuest connector Build Work item and change set traceability Build definitions for team and private builds Local or remote build servers Supports Ant and command line tools Integration with Rational Build Forge Single structure for project related artifacts World-class team on-boarding / off-boarding including team membership, sub-teams and project inheritance Role-based operational control for flexible definition of process and capabilities IBM Rational Jazz Team Server Team advisor for defining / refining rules and enabling continuous improvement Process enactment and enforcement In-context collaboration enables team members to communicate in context of their work 2010 IBM Corporation Lab Overview 31

19 Rational Quality Manager: A closer look IBM Collaborative Application Lifecycle Management Rational Quality Manager Quality Dashboard Requirements Management Test Management and Execution Defect Management Create Plan Build Tests Manage Test Lab Report Results Functional Testing SAP Java Performance Testing Best Practice Processes JAZZ TEAM SERVER Open Lifecycle Service Integrations Web Service Quality Code Quality.NET IBM System z, System i Security and Compliance Open Platform Third party vendors homegrown 2010 IBM Corporation Lab Overview IBM Corporation Lab Overview 33

20 Module 1 Update the Product Backlog An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Module 1 Update the Product Backlog 35

21 Objectives Explore the Rational Requirements Composer (RRC) native interface. Explore how Rational Requirements Composer can be used to create SCRUM stories and related requirement artifacts. Explore the integration between Rational Requirements Composer and Rational Team Concert (RTC) that enables creating and linking to new or existing RTC work items from RRC stories or other resource types that help ensure and track story to development work item coverage. Explore the Rational Team Concert Web interface from an analyst's point of view. Explore Rational Team Concert dashboards and viewlets. Explore how Rational Team Concert can facilitate and manage changes to project plans. Explore how Rational Team Concert can manage SCRUM story and product work item backlogs IBM Corporation Module 1 Update the Product Backlog 36 Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott (SCRUM Master) Marco (Development Lead) Deb (Developer) Tanuj (Test Lead) Describe highest priority features Define sprint goal Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint Align test sprint plan Check team alignment Develop surfer squawker Monitor integration build Create test scripts and test execution records Monitor build status Triage defects Monitor the sprint Fix defect and deliver change Execute test and submit defect Confirm defect is fixed 2010 IBM Corporation Module 1 Update the Product Backlog 37

22 Lab 1 Scenario You are "Bob," the product owner, for this entire lab. You have a new story that you want included in the coming sprint. You will create a new story requirement in Rational Requirements Composer and then create and link it to a new user story work item in Rational Team Concert (seeding a RTC development story work item from its definition in RRC). You will ensure that all story requirements targeted for the coming sprint have associated development work items (determine requirements coverage by development work items). You will prioritize the current sprint s story work item backlog in Rational Team Concert to ensure that your new story is considered for the coming sprint IBM Corporation Module 1 Update the Product Backlog 38 Lab 1 Concepts Learned Rational Requirements Composer (RRC) can be used to define and describe User Stories utilizing a variety of techniques and resource types including rich text (note cards), user interface sketches, storyboards, and flows All RRC resource types can have attributes, be tagged, and linked to each other to create a broader web of linked context to facilitate better definition and understanding of what is required from development and test. User stories and other, related requirements artifacts defined in Rational Requirements Composer can be used to create and link to new or existing development work items in Rational Team Concert (RTC). User story coverage by development work items can be assessed by utilizing and displaying the links established between RRC user stories and RTC development work items. The Rational Team Concert Web interface is a robust interface that can be used as the primary interface for many team roles. Rational Team Concert provides direct support for Scrum. Note: While this session uses Scrum, Rational Team Concert provides excellent support for a variety of development methodologies. Rational Team Concert dashboards contain interactive viewlets that provide each team member with the information they require. Projects, teams and individuals can have their own dashboards customized to their needs. Rational Team Concert makes it easy to manage a project's development plan IBM Corporation Module 1 Update the Product Backlog 39

23 2010 IBM Corporation Module 1 Update the Product Backlog 40

24 Module 2 Plan the Sprint An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Module 2 Plan the Sprint 42

25 Objectives Further explore the Rational Team Concert Web interface as well as Rational Team Concert dashboards and viewlets. Explore how Rational Team Concert enables agile teams to manage sprint/iteration plans and manage tasks. Explore how Rational Team Concert can be used to facilitate a sprint planning meeting IBM Corporation Module 2 Plan the Sprint 43 Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott (SCRUM Master) Marco (Development Lead) Deb (Developer) Tanuj (Test Lead) Describe highest priority features Define sprint goal Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint Align test sprint plan Check team alignment Develop surfer squawker Monitor integration build Create test scripts and test execution records Monitor build status Triage defects Monitor the sprint Fix defect and deliver change Execute test and submit defect Confirm defect is fixed 2010 IBM Corporation Module 2 Plan the Sprint 44

26 Lab 2 Scenario You will play three different roles in this lab! As Bob, the product owner, you will use the Rational Team Concert Web interface to describe the highest priority features to the team. As Scott, the scrum master, you will use the Rational Team Concert Web interface to create a plan for the new sprint and add stories to the plan. As Marco, the development lead, you will use the Rational Team Concert Web interface to create development tasks for each item in the sprint plan and assign them to developers IBM Corporation Module 2 Plan the Sprint 45 Lab 2 Concepts Learned For teams using Scrum, Rational Team Concert can be an integral tool in the sprint planning meeting. It provides views (Product Backlog, Taskboard) and viewlets (Team Velocity) that are essential to Scrum. Rational Team Concert makes it easy to create new sprint/iteration plans and add work to them, or move items from one plan to another. For Scrum, stories can link to one or more development tasks that can be used to assign work to developers IBM Corporation Module 2 Plan the Sprint 46

27 2010 IBM Corporation Module 2 Plan the Sprint 47

28 Module 3 Manage the Sprint An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Module 3 Manage the Sprint 49

29 Objectives Explore "collections" in Rational Requirements Composer and how they can be used as an input to test planning in Rational Quality Manager. Explore how a team using Rational Team Concert and Rational Quality Manager can collaborate to integrate testers with the development team and ensure test coverage. Explore the Rational Quality Manager interface. Explore associating a test plan in Rational Quality Manager with a requirements collection in Rational Requirements Composer. Create a new test case in Rational Quality Manager and associate it with a story in Rational Team Concert. Explore how Rational Team Concert can be used to track project status and find impediments to progress. Create a query in Rational Team Concert that verifies traceability from requirements to development to test IBM Corporation Module 3 Manage the Sprint 50 Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott (SCRUM Master) Marco (Development Lead) Deb (Developer) Tanuj (Test Lead) Describe highest priority features Define sprint goal Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint Align test sprint plan Check team alignment Develop surfer squawker Monitor integration build Create test scripts and test execution records Monitor build status Triage defects Monitor the sprint Fix defect and deliver change Execute test and submit defect Confirm defect is fixed 2010 IBM Corporation Module 3 Manage the Sprint 51

30 Lab 3 Scenario You will play three different roles in this lab! As Bob, the product owner, you will use Rational Requirements Composer to create a collection of requirements artifacts that relate to the current sprint. As Tanuj, the test lead, you will use Rational Quality Manager to update the sprint test plan and associate it to the collection of sprint artifacts in Rational Requirements Composer. As Scott, the scrum master, you will use Rational Team Concert to check the alignment of the sprint plan with requirements and test plan 2010 IBM Corporation Module 3 Manage the Sprint 52 Lab 3 Concepts Learned Rational Requirements Composer, Rational Team Concert and Rational Quality Manager work together to help all team members stay in sync with the development plan. Rational Requirements Composer, Rational Team Concert and Rational Quality Manager give users of each tool visibility into data from the other tools, and link items from each of the tools together IBM Corporation Module 3 Manage the Sprint 53

31 2010 IBM Corporation Module 3 Manage the Sprint 54

32 Module 4 Implement the Sprint Plan An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Module 4 Implement the Sprint Plan 56

33 Objectives Explore how Rational Quality Manager can be used to associate test implementations (scripts) with test cases. Explore the Rational Team Concert Eclipse interface from a developer s perspective. Understand how to use Rational Team Concert to accept work, complete development tasks and deliver updated work to the team. Explore the team build features of Rational Team Concert. Explore how all team members can monitor the status of team builds, regardless of whether they use Rational Team Concert or Rational Quality Manager IBM Corporation Module 4 Implement the Sprint Plan 57 Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott (SCRUM Master) Marco (Development Lead) Deb (Developer) Tanuj (Test Lead) Describe highest priority features Define sprint goal Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint Align test sprint plan Check team alignment Develop surfer squawker Monitor integration build Create test scripts and test execution records Monitor build status Triage defects Monitor the sprint Fix defect and deliver change Execute test and submit defect Confirm defect is fixed 2010 IBM Corporation Module 4 Implement the Sprint Plan 58

34 Lab 4 Scenario You will play two different roles in this lab. As Tanuj, the test lead, you will use Rational Quality Manager to create and edit new test scripts and test execution records for the test cases you added in the previous lab. As Deb, the developer, you will use the Rational Team Concert Eclipse interface to plan your work, complete your development tasks, deliver your updates to the team and execute an integration build on the team's build server. As Tanuj (again), you will use Rational Quality Manager to monitor the team build status and deploy the built application (following a test script) so that the application is ready for test IBM Corporation Module 4 Implement the Sprint Plan 59 Lab 4 Concepts Learned Jazz Source Control provides private repository workspaces to track and back up your changes before you share them with the team using a stream for integration Rational Quality Manager test scripts implement test cases that can be linked to the drivers for those test cases (in this case, stories). Rational Quality Manager provides a highly descriptive manual testing facility that provides the tester with the right level of detail required to execute the test correctly. Rational Team Concert queries make it simple for any team member to see what they need to work on. A change set is the fundamental unit of change and collaboration in your team environment. Change sets are migrated between streams via two operations: accepting and delivering. This team did not require work items to be associated with delivered changes, but that could be turned on. Developers can run "personal builds" on the team's build server to ensure that the code they see in their workspace successfully builds using the team's build process. Ensuring compilation in the integrated development environment (IDE) isn't always enough. Team members can request a "team build" that will grab the latest code on the team's integration stream and build it on the team build server. Every team member has access to build data from team builds. This promotes communication and collaboration among the contributors on local or remote sites IBM Corporation Module 4 Implement the Sprint Plan 60

35 2010 IBM Corporation Module 4 Implement the Sprint Plan 61

36 Module 5 Respond to a Test Failure An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Module 5 Respond to a Test Failure 63

37 Objectives Explore how Rational Quality Manager can be used to execute manual tests, log test results and generate defects for the development team to fix. Explore how Rational Team Concert can be used to triage defects and help determine who should be assigned new work. Further explore how a developer uses Rational Team Concert to discover new work assigned to them, fix defects, deliver fixes to the team and work with team builds. Explore how a tester can use Rational Quality Manager to monitor the team build status, determine what work is included in a new build and verify that defects have been fixed IBM Corporation Module 5 Respond to a Test Failure 64 Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott (SCRUM Master) Marco (Development Lead) Deb (Developer) Tanuj (Test Lead) Describe highest priority features Define sprint goal Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint Align test sprint plan Check team alignment Develop surfer squawker Monitor integration build Create test scripts and test execution records Monitor build status Triage defects Monitor the sprint Fix defect and deliver change Execute test and submit defect Confirm defect is fixed 2010 IBM Corporation Module 5 Respond to a Test Failure 65

38 Lab 5 Scenario You will play three different roles in this lab! As Tanuj, the test lead, you will use Rational Quality Manager to execute a manual test, denote that the test failed and generate a new defect related to the test result. As Macro, the development lead, you will use the Rational Team Concert Web interface to analyze the new defect, determine who should fix the defect and assign the defect. As Deb, the developer, you will use the Rational Team Concert Eclipse interface to determine that there is a new defect assigned to you, analyze the test result related to that defect, resolve the defect and request a new team build. As Tanuj (again), you will notice the new build result, determine what is fixed in that build, deploy the new build and verify that the defect you created is indeed fixed IBM Corporation Module 5 Respond to a Test Failure 66 Lab 5 Concepts Learned The Rational Quality Manager manual test facility allows the test to document stepby-step test results as the test is being executed, including grabbing helpful screen snapshots that may be useful in debugging. Test results can document the build that was used for the test, to aid in debugging. Defects can be created from test results and routed to the development team. Defects created from test results are automatically linked back to the test result, to aid in debugging. Testers can denote which defects are preventing (blocking) test cases from succeeding ensuring they don't waste time executing the same test and generating duplicate defects. This also helps testers monitor the defects they've generated so they know when it's worthwhile to run the test again. Rational Team Concert queries make it easy for team leads to find new work and determine the appropriate person for assignment. Change sets can be associated with work items to denote which artifacts were modified to implement a work item IBM Corporation Module 5 Respond to a Test Failure 67

39 2010 IBM Corporation Module 5 Respond to a Test Failure 68

40 Group Module 6 Monitor the Sprint An IBM Proof of Technology 2009 IBM Corporation Agenda Group Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2009 IBM Corporation Module 5 Tracking Status 70

41 Objectives Group Explore how Rational Requirements Composer, Rational Team Concert and Rational Quality Manager can be used by various team roles to gain insight into the aspects of project status that are important to them. Further explore dashboards, viewlets and queries in all three solutions. Learn how to export information to various formats IBM Corporation Module 5 Tracking Status 71 Group Lab Sequence of Events Bob (Product owner) Create new requirement and elaboration artifacts Review requirements for the sprint Update product backlog Scott (SCRUM Master) Marco (Development Lead) Deb (Developer) Tanuj (Test Lead) Describe highest priority features Define sprint goal Agree to items for the backlog Add development tasks Create collection of artifacts for the sprint Align test sprint plan Check team alignment Develop surfer squawker Monitor integration build Create test scripts and test execution records Monitor build status Triage defects Monitor the sprint Fix defect and deliver change Execute test and submit defect Confirm defect is fixed 2009 IBM Corporation Module 5 Tracking Status 72

42 Group Lab 6 Scenario You will play the role of various team members as they use Rational Requirements Composer, Rational Team Concert or Rational Quality Manager to gain access to the data they need to monitor project status IBM Corporation Module 5 Tracking Status 73 Group Lab 6 Concepts Learned Rational Requirements Composer, Rational Team Concert and Rational Quality Manager provide excellent reporting facilities within and across the solutions IBM Corporation Module 5 Tracking Status 74

43 Group 2009 IBM Corporation Module 5 Tracking Status 75

44 Session summary An IBM Proof of Technology 2010 IBM Corporation Agenda Introduction to Collaborative Application Lifecycle Management (C/ALM) Lab Overview Module 1 Update the Product Backlog Module 2 Plan the Sprint Module 3 Manage the Sprint Module 4 Implement the Sprint Plan Module 5 Respond to a Test Failure Module 6 Monitor the Sprint Session Summary 2010 IBM Corporation Session Summary 77

45 Session summary We have described current collaboration challenges with distributed teams We have explored how Rational Requirements Composer, Rational Team Concert and Rational Quality Manager can: Enable teams to collaborate in real time in the context of the work they are doing, especially in globally diverse environments Enable projects to be managed more effectively by providing visibility into accurate project information drawn directly from actual work Automate traceability and auditability by managing artifacts and their interrelationships across the life cycle, empowering teams to deliver more value We have provided a hands-on experience using these products to automate the software delivery process 2010 IBM Corporation Session Summary 78 Next steps Engage your local Rational team Provide a customized demo for your team Conduct a targeted proof of concept Register on jazz.net and explore learning tutorials and videos IBM Corporation Session Summary 79

46 Additional resources Learn more about and download free trials of Rational Requirements Composer, Rational Team Concert and Rational Quality Manager Explore tutorials, demos and other developer learning resources Participate in the open commercial development of Jazz by joining the community Learn more about the Jazz technology and the future IBM Rational product roadmap IBM Corporation Session Summary IBM Corporation Session Summary 81

47 We appreciate your feedback in order to improve this educational event. Please fill out the survey form IBM Corporation Session Summary 82

48 Copyright IBM Corporation The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. This information is based on current IBM product plans and strategy, which are subject to change by IBM without notice. Product release dates and/or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at ibm.com/legal/copytrade.shtml Other company, product and service names may be trademarks or service marks of others.