|
|
Agile Development Conference & Better Software Conference West 2012: Patterns of "Big" Scrum Software development organizations adopting Scrum have struggled to apply it to big projects with multiple teams. Dan Rawsthorne is frequently asked, “What does ‘big’ Scrum look like?” Because no two organizations are alike, this simple question does not have a simple answer. However, Dan has discovered patterns that are common in organizations that successfully implement “big” scrum. The first pattern he explores-Product Owner Team-allows the organization to handle agility up and down the hierarchy. Dan also discusses the Cross-cutting Teams pattern that handles issues-architecture, usability, integration, performance, and evaluation-that the formal hierarchy can’t resolve. Finally, Dan discusses the BuddyUp pattern to describe the best way to work with subject matter experts from dispersed parts of the organization.
|
Dan Rawsthorne, Consultant
|
|
|
A Crash Team Approach to Effective Testing Rapid changes and stunted delivery deadlines are always challenging software testers. To catch up, software testing must take a different approach without cutting corners-hence, the crash team. The crash team approach focuses on integration testing and runs in parallel with functional testing. Its technique discovers system problems early, problems that would be hard to find with traditional methods. It also supports the spiral development model that's been adopted in many rapid application development environments.
|
Pei Ma, WeiMa Group LLC
|
|
|
Testing The Chain: End-to-End Integration Test When processes include several applications, the testing process is complicated in many ways. Possible complications include: organizational issues because of the multitude of test teams and their interdependencies; processes and transactions that span the chain which require new test scenarios; integral design, information analysis, and process design documents that aren't fit for the purpose of chain testing; and test execution that demands integral knowledge of the chain. This session gives you a list of all the variables that need to be considered, then offers solutions for successfully organizing chain testing.
|
Gerard Numan, POLTEQ, B.V.
|
|
|
Basis Path Testing for Structural and Integration Testing Basis path testing is a structural testing technique that identifies test cases based on the flows or logical paths that can be taken through the software. A basis path is a unique path through the software where no iterations are allowed; they're atomic level paths, and all possible paths through the system are linear combinations of them. Basis path testing uses a Cyclomatic metric that measures the complexity of a source code unit by examining the control flow structure. Basis path testing can also be applied to integration testing when software units/components are integrated together. You'll see how the use of the technique quantifies the integration effort involved as well as the design-level complexity.
|
Theresa Hunt, The Westfall Team
|
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.
