P. 1
Agile White Paper

Agile White Paper

|Views: 21|Likes:
Published by kallamsrs

More info:

Published by: kallamsrs on Oct 23, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Successful Agile with HP Quality Center

Market leading software for Quality Assurance

Table of contents
Becoming agile and its challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 How HP Quality Center software supports agile software development . . . . . . . . . . . .5 How HP QuickTest Professional supports agile software development . . . . . . . . . . . . . . .7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 For more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Two of the most common and successful methodologies are Scrum and Extreme Programming (XP) . Key drivers for implementing agile software development processes: • Accelerating time-to-market • Enhancing software quality • Increasing productivity • Improving alignment between IT and business objectives • Improving project visibility • Reducing cost • Enhancing the ability to manage changing priorities • Reducing project risk • Reducing process complexity IT departments are tasked with increasingly diverse responsibilities in today’s economy . Without this. To make sure these challenges are overcome. and finally the Quality Assurance (QA) organization needs to ensure they are prepared to test the multi-layered applications delivered by development and that their test plans are flexible enough to accommodate the changes occurring per iteration . When done right. HP interviewed 781 IT professionals to find out who is using agile and how they implement agile processes . self-organization. and a business approach that aligns software development with customer needs and company goals . Development teams must manage increasing application complexity. Out of the remaining 31 percent. However. there is zero tolerance for downtime . HP Quality Center’s suite of solutions help teams adapt to agile by supporting various agile stakeholders and by facilitating traceability between user stories. and accountability . has led organizations to look for more iterative ways of working . achieving the goals of agile development can be tricky . 2 . In addition. multiple iterations. half plan to start using agile within the next two years . Business Analysts (BA) need to learn how to capture requirements in higher level user stories which are both more flexible and can be easily interpreted by test and development teams. One of the most popular means by which to achieve these objectives has been through the adoption of agile development . expensive and most likely fail . agile projects will be inefficient.In 2009. 24x7 operations and integrated supply chains while delivering applications to market in quicker iterations to respond to the demands of a hyper-competitive marketplace . frequent reviews. They must support global. agile best practices allow for rapid delivery of high-quality software. which in themselves advocate flexibility. Sixty-nine percent were already using agile methodologies . different test types and through defect management and integrations with third party solutions that meet the needs of development . HP Quality Center gives you the right tools to deploy high-quality applications quickly and effectively . Agile methods promote teamwork. organizations need to not only look at agile tools but if they want agile to successfully scale they must put in place best practices and process support . Critical business decisions rely on collaboration and providing all teams with visibility into the development processes . This coupled with the emergence of new technologies.

Working in short iterations and delivering the working software at the completion of each iteration provides proof to customers and additional stakeholders that an agile project is progressing . In short. successful agile projects require change at all levels and though there are big risks—if executed well. therefore making collaboration a key success criteria . It is vitally important to gain visibility across projects to allocate resources. agile can provide even bigger payoffs . Some of the main challenges of agile include: • Change in working approach by multiple groups • Pressures of new technology and the complex testing needed to support this • Many different stakeholders working together • Less time to plan • Less time to execute • Visibility into the status of the project Agile development requires work groups to change the way they approach the project and often requires teams who have been used to working in silos and in different tools to move towards a unified method of working . How agile requirements differ from traditional design requirements Traditional • Detailed requirements • Multiple functional requirements • Written mainly by BA • Multiple word documents • Long design phases • Single sign-off by BA or Product Management Agile • Focus on user stories • Prioritization is key • Multiple stakeholders collaborate to define user stories • Less time for design creation • Requirements are more iterative These challenges are often compounded by the fact that the move to agile can be quite sudden and is often driven by specific teams within the organization forcing others to adopt . Even more than this.Becoming agile and its challenges Agile requires a shift in the way an organization thinks . manage constraints and be sure that compliance requirements are addressed . visibility into the true status of a project improves the team’s ability to be successful . It impacts all stages of the software development lifecycle (SDLC) and all stakeholders within it from the BA to QA to development. 3 . Visibility into the status of an agile project is critical .

One of the final and probably most significant challenges of agile we will touch on in this paper is the challenge of time . A release is developed incrementally . the further away a date is. sprints. Increments may be called cycles. This can often lead to many stakeholders having conflicting views and the project manager becoming overwhelmed . In order to combat this the project manager must create a sense of cohesion between the stakeholders and make sure that when decisions are made that all stakeholders are appropriately informed . That means every little snag becomes a big risk . performance. However.Agile lingo: QC releases and cycles “Product” is the term used to refer to the top level folder . it is imperative . The multiple iterations of discovery can actually help drive the refinement process and make each execution successful . the more vague the agile schedule becomes . iterations. Another key problem with agile is that project managers are not only taking direction from customers but they also need to manage various development teams in unison . Even in traditional methodologies. and without automated tests. In agile projects. mainly because agile projects must adapt quickly when a project needs to change and that makes it extremely hard to plan for the future . Repeatable QA testing significantly lowers the risks of agile software design. Agile projects are done on a compressed timeline . Less time to plan equates to less time to execute . This compacted schedule further drives the need for better team collaboration . Project QA needs to be validated from every aspect—functional. and that repeatability needs to be tested both manually and automatically. “Release” is typically a product version. Continuous QA testing can help mitigate that risk . managing multiple conflicting stakeholders can be tricky and political . and so on according to the development paradigm . no team can finish the regression testing and exploratory testing needed to deliver high-quality software in such short intervals . Traditionally in agile projects there is less time to plan than with traditional software development projects. In addition to this. and security—it needs to be repeatable. 4 . The already high pressures of implementing new technologies and the complex testing they need are compounded by agile methodologies . many teams struggle to get traction on test automation often because of the perceived high costs and time associated with automation as a whole . The assignment of items to a specific release and cycle is used to track the progress of the iteration and to identify items for reporting across the cycles . And those small increments are also beneficial in projects where the requirements are volatile or poorly understood .

5 . automated. HP Quality Center in action HP Quality Center shows you the entire team’s efforts in one clear view . Benefits of HP Quality Center • Customizable Fields and Attributes for additional information • Modular Data Storage Structures • Release and Cycle Management for SPRINT and backlog support HP Quality Center helps your organization: • Gain real-time visibility into requirements coverage and associated defects to paint a clear picture of • Custom Requirements Types for user stories and tasks business risk • Manage the release process and make more informed release decisions with quality tracking and reporting • Measure progress and effectiveness of quality activities • Collaborate in the software quality lifecycle with a single global platform • Manage manual. and SOA testing assets centrally • Facilitate standardized testing and quality processes that boost productivity through workflows and alerts • Lower costs by using QA testing tools to capture critical defects before they reach production • User Role Configuration to support agile roles such as the Scrum master • Custom Workflow and Field Transition Rules • Custom Reports for work tracking and velocity How HP Quality Center software supports agile software development Both HP Quality Center software and the HP Quality Center suite of products help agile teams to manage their needs throughout the application lifecycle providing customers with the right tools to deploy high-quality applications quickly and effectively .Figure 1.

Because agile timelines are so tight. while providing an audit history of changes throughout the project lifecycle . Velocity (Microsoft Excel) and defect rate. users can make real-time decisions based on application status across projects and QA initiatives . HP Quality Center can also export a report source into Microsoft Excel. Baselining allows you to capture a group of requirements. Having this visibility is essential when multiple stakeholders are working on the same asset in fast-paced agile iterations . tests. This allows you to keep track of both the actual effort spent and the remaining effort within current and future iterations . tests and defects provides QA managers. Specific features of HP Quality Center include: • Asset Sharing: The ability to share assets between Quality Center projects including user stories. To enable this HP Quality Center provides an inbuilt Risk-Based Quality Management Methodology which allows users to objectively assess testing priorities . and align business and IT on what tests need to be developed . • Versioning and baselining: Versioning allows distributed teams to collaborate and manage multiple versions of test assets in parallel. or test assets at strategic points in the project lifecycle to mark specific milestones . and the rest . letting your end users perform endless data manipulation . The requirements module in HP Quality Center is used to define and prioritize user stories. You can compare baselines to assess the impact of changes and enable rollback of assets.Each of the modules within HP Quality Center can be tailored and leveraged by agile teams: • Management Module (formerly Releases and Cycles): can be used to manage the sprint and product backlogs. Burn Down. • Traceability: Being able to effectively link and trace user stories. track progress of the iterations—how many tests are left to run over what timeframe. and track the quality of the iterations— how many outstanding defects are there which need to be addressed in upcoming sprints . user story status (dashboard). 6 . define the tasks which represent the work items associated with a user story lead. tests (manual and automated) and business components facilitates collaboration and accelerates agile development . By leveraging the inbuilt and customizable reports in HP Quality Center customers can generate and view agile reports such as Burn Up. • Requirements Module: Agile requirements are generally referred to as user stories . the business and developers visibility into the impact and inter-relationships of what they are working on . effectively prioritizing which user stories and tests need to be assigned to which iterations and sprints is vital to addressing the most important user stories early in the release . Different baselines can be pinned to different test sets to allow parallel development—an essential component of agile in large organizations that manage multiple releases at one time as part of an organization-wide initiative . • Test Lab: Used to execute the manual tests • Test Plan: Used to plan test iterations • Dashboard and Microsoft Excel Reporting: The ability to track progress in agile is vital . if required . Also with HP Quality Center’s centralized reporting.

while providing advanced functionality for tester collaboration . HP Quality Center and HP Functional Testing software provide Web-based. How HP QuickTest Professional supports agile software development HP QuickTest Professional software automates functional regression test automation on a Web or client-based desktop computer application . testers can build test cases by capturing flows directly from the application screens and applying robust capturing technology (record/replay) . and business processes • Fully document and replicate defects for developers. verifies and replays user interactions automatically and helps testers quickly identify and report on application effects. Using HP range of automated test tools from HP QuickTest Professional to HP Business Process Testing to HP Service Test for SOA. automated software quality testing. HP QuickTest Professional offers a fresh approach to automated testing: it deploys the concept of keyword-driven testing to radically simplify test creation and maintenance . data sets. QA teams and agile stakeholders can: • Be empowered to create sophisticated test suites with less training • Establish correct functionality across all environments. It captures. The software modules provide the visibility needed to validate both functionality and automated business processes—and identify bottlenecks in production that hamper business outcomes . Using keyword capabilities. HP Quality Center in action HP Quality Center helps estimate effort needed and expended on user stories and tasks . The HP Quality Center suite enables agile teams to engage in application testing even before the development process is complete.Figure 2. which helps accelerate release schedules while maintaining quality . Power users get full access to the underlying test and object properties through an integrated scripting and debugging environment that is synchronized with the Keyword View capability for your complete testing cycle . 7 . helping them fix defects faster and meet production deadlines • Easily regression test ever-changing applications and environments • Deliver quality products and services and improve revenues and profitability • Enable tester workgroups to share automated testing assets across teams Together. integrated systems for requirements management. and defect management across a wide range of application environments .

schedules. Multi-dimensional traceability is supported between user stories. requirements coverage • Make go-live decisions with confidence • Standardize and manage the entire quality process • Reduce application deployment risk • Improve application quality and reliability • Manage application change impact through manual and automated functional testing • Provide quality in strategic sourcing initiatives • Develop a warehouse of critical application quality project data The HP Quality Center suite provides real-time visibility of requirements coverage and associated defects to evaluate quality and business risk . The information contained herein is subject to change without notice . Backlog. July 2009 .com/go/quality © Copyright 2009 Hewlett-Packard Development Company. and User story • Can be tailored to user and project needs—Tasks.hp. There are frequently challenges among stakeholders. if it is not implemented properly customers can run the risk of increasing costs and loss To learn more. Agile software development is quickly becoming the preferred way to build mission-critical software For more information systems . problems with communication. HP Quality Center allows you to enhance your application development processes to take advantage of the benefits of agile . and various types of testing each with its own set of requirements. a change impact report provides visibility into the other assets affected.com/go/quality of quality instead of making teams more effective . burn-up/down charts. and spent hours • Can be used by all project stakeholders—Testers. across releases and iterations . globally accessible. estimation. business analysts. Technology for better business outcomes To learn more.hp . Use HP Quality Center to get flexible . planning. Nothing herein should be construed as constituting an additional warranty . tests and defects. you can: HP Quality Center supports agile development and testing • Supports agile practices—Scrum methodology: Sprint. enabling you to avoid a full regression test after each change . The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. and the like • Can be used along the entire project lifecycle—From planning to delivery. testing included • Reports project progress and delivered value—Project and cycle progress. developers. The complexity of testing is increasing as applications themselves become more complex and initial testing is increasingly difficult—trying to run all these tests in an agile environment compounds the problem even further . visit www . When a user story changes. However. Dispersed teams also receive prompt notification of any changes that might impact their own tasks .P .With HP Quality Center. and procedures . HP shall not be liable for technical or editorial errors or omissions contained herein . Web-based software platform . 4AA2-7240ENW. Summary HP Quality Center streamlines the end-to-end quality process— from requirements management through test execution and defect management—into one. L . compressed schedules. By defining dependencies among tests you can realistically emulate real-life business processes and make it easier to maintain and reuse the tests . visit www.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->