23

iQCXGlobalResRULES (1)

Embed Size (px)

DESCRIPTION

Presentation from Cornerstones 2011 Customer Conference in Memphis

Citation preview

Page 1: iQCXGlobalResRULES (1)
Page 2: iQCXGlobalResRULES (1)

iQCX Global ResRULES

Page 3: iQCXGlobalResRULES (1)

iQCX Global ResRULES• Understanding ResRULES: the heart of iQCX• Graphical Workflow: new view to more clearly

define your reservation process and methodology.

• Global ResRULES: define specifications and design structures to create simple assessments

• Best Practices: tips and tricks on how to make ResRULES reusable and easy to maintain

Page 4: iQCXGlobalResRULES (1)

How do we get there?

• Simplify from the top to the bottom.• Each piece to the point, smaller pieces.• Don’t bleed, finish the current before you start the

next piece.• Keep it flexible.• Keep asking ‘Show me’. Tangible, meaningful results

and expectations.

Page 5: iQCXGlobalResRULES (1)

Maturity pays off

Global ResRULES Defined• What are they? Libraries of reusable functions and data

elements• Why now? Maturity and experience have given us a

strong understanding of how our customers are using the system and how to achieve better efficiencies

• Benefits? More efficient and meaningful progression that can be captured and reused

Page 6: iQCXGlobalResRULES (1)

Keeping it AgileSummary points from The Twelve Principles of Agile Software

(Agile Manifesto)• Satisfy the customer through early and continuous delivery of

solutions.• Welcome changing requirements, even late in the process. • Deliver working solutions frequently with a preference to the

shorter timescale.• Results are the primary measure of progress.• Simplicity--the art of maximizing the amount of work not done--

is essential.• Often stopping to tune and adjust behavior accordingly.

Page 7: iQCXGlobalResRULES (1)

Before we write the RulesINVEST (Independent, Negotiable, Valuable, Estimable, Small,

Testable) to get your story straight at the beginning• Independent – One ResRULE Group should be independent of

another (as much as possible). Keep the story simple• Negotiable - A user story is negotiable• Valuable - Each story has to be of value to the customer• Estimable - The developers need to be able to estimate• Small - A good story should be small in effort• Testable - A story needs to be testable for the "Confirmation" to take

place

Page 8: iQCXGlobalResRULES (1)

Where You Will Live

Page 9: iQCXGlobalResRULES (1)

What/Where/When• Travets are real

time windows • Filter to determine

the level of data inspection

• Filter to location in your work flow

•Watch your process live or any place in

time

Page 10: iQCXGlobalResRULES (1)

From the top…

Page 11: iQCXGlobalResRULES (1)

Breaking it all down…

Page 12: iQCXGlobalResRULES (1)

Breaking Down: Main Window• Schedule and

ResRULES information at both a high and low level.

• Ability to dig into specific information easily and quickly.

Page 13: iQCXGlobalResRULES (1)

Keep digging…In this case I’ve put the mouse over an action,

that will give you more detailed

information about the action itself.

Page 14: iQCXGlobalResRULES (1)

And digging…Functional Points and

Access Points determine the color coding used to help visually recognize where your data and

functional decision points exist in your process

Page 15: iQCXGlobalResRULES (1)

Function Point• Function Point is picked at the ResRULE level and/or higher levels such

as a group

Page 16: iQCXGlobalResRULES (1)

Access Point• Access points are determined by the physical

rules/schedules themselves. When a rule is created or altered it is tagged with all of it’s access points such as GDS.

Page 17: iQCXGlobalResRULES (1)

For the geeky ResRULE writer

The ResRULE nerds can also access a full print out of all detailed

information on any global or local process.

Page 18: iQCXGlobalResRULES (1)

How to validate versions?Workflow and ResRULES are validated through automation and manually through visual ‘side by

side’ comparisons using provided tools.

Page 19: iQCXGlobalResRULES (1)

Simplifying Configuration Management

• A security layer will control who has this power but once it’s granted, releasing, rolling-back and version control are all possible.

Page 20: iQCXGlobalResRULES (1)

How will we protect our process?Extensive versioning allows us to recover to any point in

time, safely and quickly to any previous functionality

Page 21: iQCXGlobalResRULES (1)

Back to the process…The recap – insuring success:• The customer has to have SIMPLE Management

of the process and direct visibility into specific aspects of their processing

• Short and more meaningful development cycles (Agile)

• Keep the testing and verification cycle on point, not the time to introduce new requests

Page 22: iQCXGlobalResRULES (1)

Keep your vision intact

• If user stories are ‘legos’ always make sure that you are building towards the larger model. Every piece is important but don’t build the walls before you finish the interior. It is easy to get caught up in smaller cycles and it’s fun but keep an eye on the ‘prize’

Page 23: iQCXGlobalResRULES (1)