Set your residual analysis project in motion.
Residuality theory for software systems design collects residues—the people, software, and information flows that remain when a software system is exposed to stress—to ease managing complexity and improve system behavior early in the design phase, building in robustness and resiliency along the way.
How can you get started with residual analysis?
The residual analysis project kickoff with Cutter Consortium Senior Consultant Barry. M. O’Reilly is an eight-hour virtual course (2 hours/day for 4 days) designed for entire project groups and intended to help you increase the likelihood of success in an early-stage project. The four interactive sessions explore the kinds of risks that normally cause a project to fail, show you how to create open discussions about project uncertainty, and help you better prepare for high-profile, hard-to-predict, rare events that are beyond the realm of normal expectations.
How will your organization benefit from residual analysis?
- Better understand project risks and requirements
- Use stress as the driver of design decisions
- Create solid input to design decisions
- Gain a clear picture of where uncertainty lies in complex projects
- Build systems that can survive stress you cannot foresee
- Utilize an alternative to formal architectural frameworks
- Identify areas of vulnerability to lessen the impact of a “black swan” event
- Study the system environment and its complex interdependencies without slowing down the design process
- Allow processes and components to organically emerge
In your residual analysis project kickoff you’ll learn how to identify and analyze stressors, and design and integrate residues. You’ll accomplish this using simple tools, without having to understand the mathematical underpinnings—all while having fun, boosting your skills, and collaborating with team members.
This course is ideal for project managers, agile coaches, architects, developers, business sponsors, developers, and requirements engineers.
Course Outline:
- Session 1
- Introduction to complexity science and software engineering: Residuality Theory
- Session 2
- Roles and technical decision making
- Identifying what we don’t know and what we think we know
- Session 3
- Stressor Analysis
- Session 4
- Design decisions and shared responsibility
- Contagion analysis
- FMEA analysis
- Next steps
What's Next?
For more information on how Barry M. O’Reilly can help your organization face its stressors head on and set your residual analysis project in motion, complete the form below or contact your Cutter Account Executive, or call +1 781 648 8700.