Paul Given
Director
CapTech Consulting
location_on United States
Member since 4 years
Share
Paul Given
Specialises In (based on submitted proposals)
Business and technology leader with over 20 years of experience merging information technology with product management, marketing, and operations to create strategic results in the financial services, travel and entertainment industries. Proven ability to provide critical solutions leveraging a lean approach coupled with strong analytical, technical and leadership skills.
Technical specialties include scaled and agile software development supporting retail, web and mobile customer interactions, employing multiple technologies to create the highest quality and best user experience.
Product management specialties include mobile and web product strategy, analog to digital product transformation, and user experience design and optimization, with a proven ability to generate a targeted vision that teams can execute.
Marketing specialties include direct marketing via digital and traditional channels, and media purchasing optimization across brands and products with a strong track record of success.
-
keyboard_arrow_down
The Three Testing Amigos
45 Mins
Case Study
Beginner
Overview
“Three Amigos” sessions are a common occurrence on many agile teams – with three or more team members exploring all aspects of a user story from the Business Value, Development, and Testing perspectives. While this helps identify gaps in user story acceptance criteria, it may not address how the respective criteria will be tested. How do we measure if we’ve “done the thing right” during development, while adding business value and considering the effectiveness and speed of testing the system?
This session provides 1) an exploration of using a Three Testing Amigos approach in agile; and 2) an interactive activity for the participants to explore potential biases and gaps in determining how a user story should be tested.
Target Audience
Agile team participants at any level of transformation.
Prerequisite
Basic understanding of Agile team ceremonies and user story generation.
-
-
keyboard_arrow_down
The Topic is code and test? Why isn't it test and code? Why does testing always get the shaft?
45 Mins
Experience Report
Advanced
Why does testing always get the shaft?
Any DevOps initiative that expects outcomes of speed and quality requires an investment mindset. Tests (unit, acceptance, non-functional, and regression) of all types are investments that can return incredible value when integrated with a software delivery pipeline.We will explore the following questions:
How do I build an organization that mines and releases the value in automated testing?
How do I, as Quality Leader in an organization, help shift the culture in my company to value consistency and predictability associated with a strong testing practice?
You may ask why this a business perspective and not a code and test perspective? This is about taking and investment mindset to testing.
-
-
No more submissions exist.
