06 operations and feedback

Module 06Feedback andOperations

Topics

Continuous Feedback

Agile techniques are effective, because they embrace continuous feedback.

Continuous feedback helps minimize the snowball effect of a fault.

Feedback loops are part of every phase of the lifecycle.

Feedback can be internal (team) or external (stakeholders).

Feedback Loops

Storyboarding and Prototyping

Supporting

the team

Validates

Business Needs

Prototypes

Simulations

Clarifies Intent

Done at thebeginning of a sprint

Create custom shapes to

re-use throughout your

application.

Create realistic mock-ups of your UI for

early approval, and attach them to work

items so developers know what to build

Hundreds of pre-built shapes,

from iOS to Windows Phone

to navigation animations

Code Reviews

Supporting

the team

Validates

Business Needs

Code Review

Code Analysis

Done ad-hocduring a sprint

Continuous User Feedback

Validates

Business Needs

Supporting the

Product

Alpha/Beta Tests

Sprint Review

At the End of a sprintor when PBI is finished.

Free Feedback client app

guides stakeholders through

the feedback process

Provide rich feedback, including

audio/video recordings,

screenshots and additional files

Automatically send

feedback requests to

stakeholders via email

Elicit actionable feedback by

focusing feedback on specific

areas of your application

Free client utility guides

stakeholders through the

feedback process

Enable detailed, rich text

feedback and a star rating system

Capture voice, video, screenshots,

attach files, or any combination

Stakeholder feedback is

captured as a work item in TFS

Create new work items based on

stakeholder feedback

Demo

Feedback ManagementPowerPoint Storyboarding

DevOps

In Production, nobody hears you scream!

Development vs. Operations

Integrated Incident Management

Operations

Development and

Testing

Production incident alert

in operations system

Assign code related incidents to development

Development system incident

reference in operations tool

Incident in development system

Request additional diagnostics from operations

Request for additional diagnostics in operations system

Generate IntelliTrace logs from within SCOM

IntelliTrace logs

collected by operations

in development system

Actionable debugging

using IntelliTrace logs

IntelliTrace in ProductionPreemptive Analytics

Gathering Actionable Data in Production

Monitor

With production errors, root causes are difficult to identify, debug and resolveIntelliTrace in Production is easy to run, and collects critical IntelliTrace logs with minimal impact to server performance. Developers, who are already familiar with using this data in test environments, now have the data to speed root cause analysis of production bugs, and rapidly identify the needed code fix.

Actionable diagnosticsIntelliTrace in Production speeds up debugging and shortens code fix times.

IntelliTrace in Production

Instrumentation in minutes with Dotfuscator injection

Extensible rules detect and prioritize production

incidents reflecting organizational priorities

Work Items are created and updated in near real-time

ensuring efficient, feedback driven response across

.NET, JavaScript, C++, Java and mobile surfaces

Monitor applications across enterprise domains and

onto external networks and consumer devices.

Enforce opt-in policy, manage dropped networks

and secure data on the wire.

Collect custom data and monitor unhandled,

caught and thrown exceptions.

Work Items are automatically created or updated when patterns are

detected in production.

Rules are easily mapped to instrumented applications

and can be reused, extended and developed to capture

business priorities and integrate with other systems

including CRM, ERP and other mission-critical platforms.

Demo

IntelliTracePreEmptive Analytics

To learn from experience gained during this test and to preserve testware for reuse in a future test. The point here is that with changes and associated maintenance tests, the testware only requires adjustment, so that it is not necessary to design a completely new test. During the test process, efforts are made to keep the test cases corresponding with the test basis and the developed system. If necessary, the selected test cases should be updated.

http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/completion-phase

The Completion Phase