This document outlines the topics and slides for a presentation on developing an effective scope of work for control system projects. It discusses the importance of clearly defining objectives, requirements, and expected outcomes upfront. Without a well-developed scope of work, projects can face issues like cost overruns, missed deadlines, and dissatisfied customers due to misaligned expectations. The presentation provides examples to illustrate how capturing details about user needs, technical requirements, and special requests is crucial for meeting expectations and achieving project success and customer satisfaction. It emphasizes validating the scope of work with all stakeholders to establish a shared understanding before beginning the implementation.
Behavior-driven development (BDD) is an evolution of test-driven development (TDD). It shifts the vocabulary from being test-based to behavior-based and positions itself as a design philosophy. JBehave is a Java framework for BDD, and this session explores how to write integration tests for your Java EE apps with JBehave. It also demonstrates how to leverage the Context and Dependency Injection (CDI) APIs to implement your tests.
This session is a must-see for all Java EE developers who want a better way to write integration tests aligned with the intended behavior.
Model driven development using smart use cases and domain driven designSander Hoogendoorn
Short presentation of how smart use cases and domain driven design can trigger model driven development. Note: there is a very good white paper on the Capgemini website about the same approach.
Behavior-driven development (BDD) is an evolution of test-driven development (TDD). It shifts the vocabulary from being test-based to behavior-based and positions itself as a design philosophy. JBehave is a Java framework for BDD, and this session explores how to write integration tests for your Java EE apps with JBehave. It also demonstrates how to leverage the Context and Dependency Injection (CDI) APIs to implement your tests.
This session is a must-see for all Java EE developers who want a better way to write integration tests aligned with the intended behavior.
Model driven development using smart use cases and domain driven designSander Hoogendoorn
Short presentation of how smart use cases and domain driven design can trigger model driven development. Note: there is a very good white paper on the Capgemini website about the same approach.
The goal of this presentation is to give attendees a deeper understanding of usability testing so they can leverage it in their own work. The material will shed light on what is important to the research buyer and will help the research provider to better understand how to plan, moderate, and report on a usability study. It will also provide information on where they can go to learn more about this very practical qualitative method.
Kay will cover what a usability test is and when to use it, the key planning steps, the language around it, and the unique insights this method produces. She will also discuss the various approaches a market researcher can take when running a usability study at different points in a product’s development (e.g., concept, early prototype, released product).
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
How to implement a theory of correctness in the area of business processes an...Universität Rostock
Conference presentation given by Niels Lohmann on September 16, 2010 in Hoboken, NJ, USA at the Eighth International Conference on Business Process Management (BPM 2010).
My presentation on Exploratory Testing at CzechTest in Prague on June 25, 2015. Experiences and some material from our Knowit course with the same title.
uTest and Crowdsortium Webinar: Scope & BriefsCrowdsortium
Have you ever pondered on how you might be able to better engage your crowd on projects or jobs? You might call it a “campaign description,” “brief,” or project “scope,” but whatever your name is, this presentation is for you. Thought leader, Matt Johnston, CMO of uTest, discuses the ways in which we reach out to our crowd.
A few questions explored:
- What formats do you use and find most effective?
- What methods are used for distribution?
- How do you guide remote workers, and how much direction is needed?
- How might we engage clients to understand the value of campaign descriptions?
Patching is Your Friend in the New World Order of EPM and ERP CloudDatavail
Historically, patching was an IT effort to stay on the support path or remove vulnerabilities. Today, in the EPM Cloud market, patching is so much more. This presentation will review several case studies of how clients received free capacities in their patches. Be a hero and make business change.
The goal of this presentation is to give attendees a deeper understanding of usability testing so they can leverage it in their own work. The material will shed light on what is important to the research buyer and will help the research provider to better understand how to plan, moderate, and report on a usability study. It will also provide information on where they can go to learn more about this very practical qualitative method.
Kay will cover what a usability test is and when to use it, the key planning steps, the language around it, and the unique insights this method produces. She will also discuss the various approaches a market researcher can take when running a usability study at different points in a product’s development (e.g., concept, early prototype, released product).
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
How to implement a theory of correctness in the area of business processes an...Universität Rostock
Conference presentation given by Niels Lohmann on September 16, 2010 in Hoboken, NJ, USA at the Eighth International Conference on Business Process Management (BPM 2010).
My presentation on Exploratory Testing at CzechTest in Prague on June 25, 2015. Experiences and some material from our Knowit course with the same title.
uTest and Crowdsortium Webinar: Scope & BriefsCrowdsortium
Have you ever pondered on how you might be able to better engage your crowd on projects or jobs? You might call it a “campaign description,” “brief,” or project “scope,” but whatever your name is, this presentation is for you. Thought leader, Matt Johnston, CMO of uTest, discuses the ways in which we reach out to our crowd.
A few questions explored:
- What formats do you use and find most effective?
- What methods are used for distribution?
- How do you guide remote workers, and how much direction is needed?
- How might we engage clients to understand the value of campaign descriptions?
Patching is Your Friend in the New World Order of EPM and ERP CloudDatavail
Historically, patching was an IT effort to stay on the support path or remove vulnerabilities. Today, in the EPM Cloud market, patching is so much more. This presentation will review several case studies of how clients received free capacities in their patches. Be a hero and make business change.
Mastering BDD - Eran Kinsbruner Workshop Quest 2018
Is43 Developing A Control System Scope Of Work Talking Points
1. IS43 Developing a Control System Scope of Work – Talking Points
Item Topic Slides Notes
1 Introductions 1-2 • Personal introduction
• Poll audience for industry affiliations
• Course outline
2 Overview 3 • What is a scope of work?
o Components, characteristics
o Defines the objectives of a project
o Identifies how to get to the end result
o Describes what the end product looks like
• Goal – Customer Satisfaction
• Parallel to a product specification
o Example of a product or outcome that can be
seemingly achieved in different ways; however, not
necessarily meeting the same criteria
• Compare tangible to intangible products
3 Lead In 4-7 • Who can relate to this situation?
• Why isn’t info available?
• What are the difficulties or stumbling blocks?
• How are the parameters of a project established without
clear objectives?
4 Challenges 8 • What are the challenges involved in developing a scope
of work?
• Why are we all here at this seminar?
• Starting with drawings and ending up with functionality
• Why is this so difficult?
• What are the obstacles that we face?
5 Communication 9 • Information flow, details, effective communication is
essential
6 Recipe Analogy 10 • Preparing a recipe represents scope of work for entire
project
• Talk about parallels between receipt and scope of work
7 Unexpected Outcomes 11-12 • Example of how features or specialization can make
similar products very different
o Car
o Primary criteria
Size
Speed
Payload
Towing Capacity
Gas mileage
Color
Number of doors
Emissions
Safety
Weather conditions
Cost
o Features
Heated seats
Satellite radio
iPod interface
Sun roof
Leather seats
Third row
GPS
• Examples of product descriptions that can have many
1
2. different matched results that are different
o Cell phone
More features and options do not always
mean more value or satisfaction
8 Purpose for a Scope of 13-14 • Usage, role, effect, benefits
Work • Balance triangle
• Checklist, path
9 Problems due to a lack of 15-16 • Misaligned expectations
Scope of Work • Cost overruns
• Missed deadlines
• Dissatisfied customers
• Loss of reputation and trust
10 Expectations 17 • How many people can relate to this experience?
• How does this relate to the scope of work?
10 Sample of bid spec Scopes 18-21 • Share samples
of Work • Discuss good, bad, ugly
• How can this be addressed more effectively?
11 Effective Scope 22 • Who defines it?
• How is it approached?
• What makes it effective?
12 Obtaining Information 23 • What is needed?
• How do you get the details?
13 Specifying Your Home- 24 • Partner audience
Exercise Example • One person is a home buyer and the other is a builder.
• The builder needs to specify a house that meets the
buyer’s needs, requests, and expectations
14 Purchasing a Laptop- Story 25 • Buying a laptop
Example • Different users have different needs
• What are the important criteria to achieve satisfaction
and work within constraints?
15 Exercise Recap/ 26 • What was the outcome?
Conclusions • How accurate was the specification?
• Would the builder specify the same house for
themselves?
• What is common about the information needed to get the
desired result?
• Exercise lessons
o Demonstrate the details and variables involved in
obtaining the desired result
o Demonstrate the approach to defining the specific
requirements
o Demonstrate how products can serve the same
purpose but be drastically different
o Demonstrate how products that may be same in
concept don’t meet different peoples’ needs
o Demonstrate the differences between interacting with
an experienced client and an inexperienced client
16 Applying Examples to AV 27 • What information is needed for defining AV functionality?
Control o Who are the users?
o What is their skill level?
o What is their technical familiarity?
o Are they used to existing systems?
o What are their specific needs?
o What are the challenges that they face?
o How will the system be used most often?
• How do we obtain the necessary information?
2
3. 18 Methods of Obtaining 28 • PDK, Quote form, Client Interview, Narrative, Samples,
Information Demo, Packages, Options
• http://designassist.avprogramming.com/login.php
• http://www.controlconcepts.net/images/quote_form.pdf
• http://www.crestron.com/downloads/pdf/programming_de
sign_kit/programming_design_kit.pdf
• http://www.amx.com/vasa/default.asp
19 Importance of Level of 29 • Features and customization
Detail • Last 10% is the difference maker
• Refer to the features in the car example
• Examples
• Password protection
• Automatic system shutdown
• Remote system monitoring
• Cable TV presets
• User modifiable dialing presets
• Web-based control
20 Recipe Story Example 30-33 • Details of the recipe make all the difference
• Recipes with the same ingredients can yield different
results
• Baking a cake – occasion, size, flavor, preferences, diet,
allergies, budget
21 Details and Variables in AV 34 • Difference in interpretation, preference, intention
Systems • Interpreting the system design and intention in different
ways
• Matrix switching, room combining, direction functionality,
presets
• The sky’s the limit
22 Documenting the Details 35 • Effectively capturing and presenting the scope of work
• Button-by-Button, Narrative, Control Spec, PowerPoint,
Active Demo, Sample System, Mock up
• http://www.controlconcepts.net/images/spec_sample.pdf
23 Validating the Scope of 36 • Balance the functionality, design, budget, timeframe, and
Work other constraints
• Establish expectations
• Confirm ability for successful outcome
• Review requirements vs. system design
• Verify hardware can support requested features
• Raise concern of possible issue when design exists
24 Responsibility for the Scope 37 • Who defines it?
of Work o Programmer or someone who knows programming.
• Who is the audience?
o Contractor, consultant, end-user, programmer –
all of the above
• When is it defined?
o Prior to design
o Prior to budget
o After design
o After budget
o After bid
o During implementation
o During acceptance testing
• How does it stand up?
o It’s only as good as the people committing to it
• Who approves it?
• How is it used?
3
4. o This is your target for completion
o Provides a blue print, script for programming,
preparation instructions
o Provide deliverable and get approval
o Ensure that all parties are on the same page
25 Applying the Scope of Work 38 • Usage
• Application
• Benefits
o Establishes requirements
o Provides guideline for programming
o Works as a checklist for testing and commissioning
o Provides validation for signoff
26 Special Requests/ Unique 39 • Customization
Criteria • Timeline, budget restrictions
• Support, changes, terms and conditions
• Source code ownership
27 Demonstrate an Effective 40 • Exercise/Example
Scope of Work and • Discuss success stories and approaches
approach and success o Define functionality requirements and user interface,
stories then specify design and equipment
o Discuss functionality in advance of implementation to
ensure that it is effectively conveyed and properly
understood.
• Audience ideas
28 Conclusions 41 • What can be done to shift the importance in a project to
the functionality requirements?
• Projects need a scope of work and the implementation
processes that go along with it.
• Reference software industry
• AV world tends to focus on getting the job done, not on
satisfaction and acceptance.
• Recap learning objectives
• We are all facing and struggling with the same difficulty.
We should work together to define guidelines for tackling
this challenge.
30 Discussion/Q&A 46-47 • LinkedIn Group: Audiovisual (AV) Control System
Solutions www.linkedin.com
4