Check out how we can Test in Agile Projects (SAP-Activate)

1. Testing in -Agile Projects (SAP- Activate)
A software testing practice that follows the principles of agile software development is called Agile
Testing. Agile is an iterative development methodology, where requirements evolve through collaboration
between the customer and self-organizing teams and agile aligns development with customer needs.
How do we perform system/validation testing ERP -SAP. Lets take a look at it………..

2. Process, iterations and Validations-Includes Speed, and Risk
Mitigation
Explore Realization Deploy RunDiscovery
SAP Activate Phases
Proj.
Prep.

3. Validate Solution – Example
Kickoff Solution
Validation
Prioritize
Deltas
Complete
documentation
Design Solution
for Deltas
Set up QA system
environment for
integration testing
Design end-user
training and begin
documentation
Design and
set-up user
roles and
security
Explore
Identify Deltas /
Make key Decisions
RoadshowCleanse
data
Execute
communications
plan
Deploy
Solution Validation
Workshops
Realize
Phase Closure
and Sign-off
Roadshow
Set up DEV
system for
configuration
User Integration
Testing
Phase Closure
and Sign-off

4. Agile in Application Lifecycle Management -Test relevant activities
Decision:RequirementstoScope
Q-Gate:ScopetoBuild
Q-Gate:BuildtoTest
Q-Gate:TesttoDeploy
Solution
Validation
2-to-4 wks
iteration cycle
Build in
Sprints
Bite Size
Pieces
Iterative
Baseline Build
Prioritized
Backlog
Gap
Identification
User stories
Integration
Test
User
Acceptance
Test
Non
Functional
Test
Build Release
Execute
Deployment
Build, Review, Unit / String
Test, Document
Business
Needs
Roadmap
Backlog /
Release
Planning
Integration
Test
Deploy
Deployment
Mode
Baseline
Scope
Validation

5. What happens during Explore Phase?
1. Reference Value
 Provide Process, Value and
Strategic Context
 Set Boundaries
 Tie to Business Case, Value
Drivers
2. Validation of SAP Solution
 Show and tell SAP
standard key design
elements
3. GAP Identification
 Identify gaps to
Standard
 Log additional scope
items
5. Delta Design
 Update Business Models
and Process Design
 Solution Design and
Visualize
6. Verify & Accept
 Verify process & solution
design
 Drive Acceptance
4. Delta Scope
Prioritization
Workshop Type A
Explore
Workshop Type B
Delta Design
7. Release &
Sprint Planning

6. Delta Gap List
 Any required and approved functionality that is not met by SAP Best
Practices, Industry Solution or Rapid Deployment Solution (RDS) will
be considered a gap. These items will be entered into the Gap List
accelerator
 Gap Types
 Configuration Gap
 Development
 Authorization Gap
 Scope Gap
 Process Gap
 OCM Gap
 Completion Considerations
 Identification of SAP gaps
 Gap Owner
 Association with SAP business process
 Priorization of log items
 Association with Sprint cycle
 SolMan Destination:
 Process level

Explore Realize Deploy RunPrepare

7. User Story Mapping – Prioritization technique
 Agile recommends to use User Oriented format
• As a <user> I want <action> so that I can <goal>.
• Includes test acceptance criteria
 Flat backlog is hard to work with
• SAP historically relies on Business Process Maps
• User Story Mapping is very similar concept –
Solution Map or Business Process Map provide
input to Story Mapping
• Plotting the requirements in story map allows you
prioritize the backlog and
• User Story Map drives release planning
(discussed later)
Scenario 1
Feature A
Feature B
Feature G
Scenario 2
Feature C
Feature D
Scenario 3
Feature E
Feature F
Feature H
Feature I
RelativeImportance
Process Flow

8. User Story Map – Visualized Release Planning
• Determine which ‘features’ are the minimal
set of requirements for first release.
• Visually document the release scope
• Validate technical and functional
dependencies (input created earlier)
• Document the release scope in backlog
Scenario 1
Feature A
Feature B
Feature G
Scenario 2
Feature C
Feature D
Scenario 3
Feature E
Feature F
Feature H
Feature I
RelativeImportance
Process Flow
Epic
Release

9. Agile Stories Spreadsheet – Sample

10. Agile Realization
Working Software
BusinessPriority
Product Backlog
MustShouldCouldWould
Priority days
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
4
5
1
8
2
7
3
4
2
2
4
3
3
6
4
5
Realize… Validate Solution
Time
Iterations / Demos
Sign-Off
(Organization
readiness)
Sprint 1
Sprint 2
String Test
Unit
Unit
Epic
Sprint 3
Sprint 4
String Test
Epic
Integration
Test
UAT
Unit
Unit
Explore RealizePrepare Deploy Run

11. Recurring Sprint Cycles- Sample

12. Prepare Explore Realize Deploy
(Pre-Assembled) DEV DEV/QA QA QA QA PROD
Project Preparation
Completion
Business Blueprint
Completion
Sprint 1 Solution Tested Start of Production
User
Acceptance
Testing
Testing Assessment
Project Testing
Strategy
Test
Plan
Unit
Testing
Epic (String)
Testing
Unit
Testing
Integration
Testing 1
Integration
Testing n
Finalize Testing
Tools & Installation
Data Migration Testing 1
Data
Migration
Testing n
Data
Migration
Testing n
Test Case Development
Test Team Mobilization &
Training
Regression Testing
Security Testing
Performance Testing
Project System
Environment
Project Milestone / Q-
Gates
Testing Work Packages
User Story Definition
Sprint n Epic
Agile – Testing Overview
Baseline Build

13. HPQC 11 integration to SolMan-Example
 HPQC11 integrated with SolMan allows us to associate requirements to test assets to defects and vice-
versa, providing a complete cycle to maintain and manage the solution. Also we can manage manual
and automated tests with accurate audit trail for compliance and analysis, as well as accelerate testing
cycles by scheduling and running tests automatically, unattended, 24x7. This in turn allows teams to
analyze application readiness at any point in the testing process with integrated graphs and reports.
 Business Process Teams providing risk-basis by way of constructing test cases for cycle/string testing
and SIT.
 Each process area will create their test cases (to standards and with guidance) to align with their most critical
business processes and requirements.
 Requirements with higher priority (based on the amount of transformation they drive in the business) will be
emphasized in system integration testing (SIT) and user acceptance testing (UAT).
 Business processes with a higher priority will be emphasized while determining test paths for SIT and UAT.
 Risk-based testing will be enhanced by way of monitoring the utilization statistics of business processes
and transactions (blueprint) through Solution Manager (SolMan). These utilization numbers will be used
to derive core functionality and to validate and maintain regression scope.
 A utilization report from SolMan Work Center identifies the T-codes and processes with highest utilization.
 SolMan adapter will map the highest utilized T-codes to test coverage in the test case scenarios in HPQC. This
mapping provides a foundation for regression scope and test cases that we would consider for automation first.

14. Thank You
Stay tune for next topic.
Sanjay Verma
Visit.help.sap.comfor other SAP information.