Pragmatic Contextual Inquiry ( John Law)

•

3 j'aime•747 vues

guest82b64d

Business Technologie

Pragmatic Voice-of-the-Customer Research Discovering Unmet Market Needs Through Simplified Contextual Inquiry by John Law Product Management View Webinar September 19, 2007

What is “Contextual Inquiry”? ,[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Purpose of contextual inquiry ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

The Iceberg What customer says they want What they really need Software Product Management / Market Research / New Product Development

What you gain ,[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Traditional contextual inquiry ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Pragmatic contextual inquiry ,[object Object],[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Methodology – 7 simple steps ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Planning – Think it through ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Recruiting participants ,[object Object],[object Object],[object Object],[object Object]

Screening candidates ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Sample screener survey Columbia University Dept. of Computer Science

Selection and scheduling ,[object Object],[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Sample email correspondence Software Product Management / Market Research / New Product Development

Observe and record ,[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

UserVue observation console Software Product Management / Market Research / New Product Development

Benefits to your product portfolio ,[object Object],[object Object],[object Object],[object Object],Software Product Management / Market Research / New Product Development

Summary ,[object Object],[object Object],[object Object],19-Sept-2007 Software Product Management / Market Research / New Product Development

Thank you ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Contenu connexe

Tendances

From a WTFinar with Container Solutions on 2020-11-19 Savvy organisations are discovering the value of treating their internal platforms as products. But what does it mean to treat a “platform as a product”? What benefits does this give, and why would an organisation adopt this approach? In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services. Using ideas & patterns from Team Topologies - including Thinnest Viable Platform, team cognitive load, and the evolutionary team interaction modes - [Matthew] [Manuel] explains how organisations like adidas and Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...

Matthew Skelton

A tour of agile tour beirut 2013

Pierre Hervouet

Product Teams Need a Family Too - Fundamental Team Topologies for Flow @ DevO...

Manuel Pais

What are some of the key differences between traditional and modern internal platforms? Many organizations have built large internal “platforms” over the years, but never achieved the benefits in speed and reduced cognitive load for their development teams that more nimble organizations increasingly showcase. Why is that? What kind of behaviors and mindset drive modern Internal Developer Platforms (IDPs) and platform teams? There is hardly a more competent DevOps thought leader on this subject than Manuel Pais, co-author of the book Team Topologies. During the webinar we will answer questions like: How do you define core goals of modern internal platforms? What are typical consumption patterns of IDPs? How can you balance between platform stakeholders vs customers?

Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021

Manuel Pais

Autonomous empowered cross-functional product teams. Sounds like a dream team, doesn’t it? So what does this mean for software delivery teams? Do we expect such a team to set up their CI/CD tooling and pipelines, automate infra, test and secure *all the things*, and, of course, run and monitor their product live? Oh wait, there’s more: they need to actually understand who their customers are, what they need from the product, what is causing friction, and what is the viability of our product as a net positive for the organization. Sounds familiar? Congratulations, you’re already playing Tetris with cognitive load! Want to know more about team cognitive load and how we can make use of effective team topologies and interactions to balance and minimize the cognitive load across an ecosystem of teams. Join this talk and climb up the cognitive load Tetris ranking with the help of one of the co-authors of the book Team Topologies: Organizing Business and Technology Teams for Fast Flow!

Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021

Manuel Pais

Beyond Agile with Team Topologies

Rich Allen

Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...

Manuel Pais

The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk I explain how and why. Key takeaways: - What is team cognitive load and why that matters - Using team cognitive load as the guiding principle for sustainable ownership and evolution of software systems - What are the fundamental topologies and interaction modes that help reduce cognitive load

Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...

Manuel Pais

Organizations that do not adapt rapidly to the modern, highly-changeable business environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, and (recently) the COVID-19 pandemic are all driving a need for business agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business agility. Matthew Skelton, co-author of Team Topologies, shares insights from organizations in several different industry sectors including banking, financial services, insurance, retail, and leisure.

Business agility with Team Topologies - NatWest Group - 2021-01-19

Matthew Skelton

Current application theory says that all responsibility for software should be pushed down to the actual DevOps-style team writing, delivering, and running the software. This leaves the EA role in the dust, seemingly killing it off. In addition to this being disquieting to EAs out there who have steep mortgage payments and other expensive hobbies, it seems to drop out the original benefits of enterprise architecture, namely oversight of all IT-related activities to make sure things don’t go wrong (e.g., spending, poor tech choices, problematic integration, etc.) and that things, rather, go right. As presented at the O'Reilly Software Architecture Conference in Berlin, November 2019.

Rethinking enterprise architecture for DevOps, Agile, and cloud native organi...

Michael Coté

From a webinar run by IT Revolution Press on 29 April 2020. Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote first team interactions with Team Topologies - IT Revolution webinar -...

Matthew Skelton

From a webinar on 29 April 2021 https://info.container-solutions.com/wtf-is-platform-as-product-2nd-edition Savvy organisations are discovering the value of treating their internal platforms as products. But what does it mean to treat a “platform as a product”? What benefits does this give, and why would an organisation adopt this approach? In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services. Using ideas & patterns from Team Topologies - including Thinnest Viable Platform, team cognitive load, and the evolutionary team interaction modes - [Matthew] [Manuel] explains how organisations like adidas and Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

What is platform as a product? Clues from Team Topologies - WTFinar with Cont...

Matthew Skelton

 Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility.  Manuel Pais is co-author of Team Topologies: organizing business and technology teams for fast flow. Recognized by TechBeacon as a DevOps thought leader, Manuel is an independent IT organizational consultant and trainer, focused on team interactions, delivery practices and accelerating flow. Manuel is also a LinkedIn instructor on Accelerating Continuous Delivery in the Enterprise. https://www.linkedin.com/in/manuelpais/

Business Agility with Team Topologies @ Digital Transformation London meetup,...

Manuel Pais

At Jenkins World 2018, Kohsuke Kawaguchi talked about the need to move away from Jenkinsteins, those single-headed monsters that eat all our food (resources) and steal our peace of mind. Jenkins X, Pipelines as Code, Configuration as Code, Evergreen, and Serverless Jenkins are all important initiatives to achieve modern, fast and reliable software delivery. However… there’s still something we need to talk about and that is team organization for effective continuous integration/continuous delivery. Should every application team own and maintain their own instances and flavors of Jenkins, since it’s all code now? Or do we still need a Jenkins admin team to handle Jenkins for everyone in the department/org so they only have to worry about their own pipelines and nothing else? Or something else, like a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs? The answer, as you probably guessed, is: it depends! But just like we are advancing our tools to become easier to install, run and update, we also need to think about how to design our teams and responsibilities for transparency and ownership of both the CI/CD system (it’s actually a product) itself and the application pipelines. This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world. Key takeaways: 1. Moving to fast, distributed, and reliable CI/CD systems is not just a matter of better tooling, but also clearer team design and responsibilities. 2. With “everything as code” for CI/CD, application teams can be empowered to own their CI/CD chains if they wish. But with great power comes great responsibility. We need to consider the teams’ cognitive capacity as well as organization size (which btw might change quickly). 3. By applying four fundamental topologies and three interaction modes from Team Topologies, we can describe different ways to split responsibility for our CI/CD system and decide which one best matches the organization and teams’ needs.

Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019

Manuel Pais

Delivery patterns for rapid and reliable releases (All Day DevOps 2018)

Manuel Pais

Mendix essentials 25 11-2011 introductie mendix by arno rood

Mendix

Continuous Delivery practices have increasingly become “table stakes” for effective software delivery since the publication of the book Continuous Delivery by Jez Humble and Dave Farley in 2010. The combination of sound technical practices and a scientific approach to testing and feature development has led to significant success with software delivery with organisations around the world. However, in large organisations with many teams and many different suppliers, there are also many ideas about what Continuous Delivery is. This variety of approaches and assumptions can lead to conflicts around deployments, testing, releasing, and operations, resulting in a macro-level sub-optimal flow of change. In this talk, Matthew Skelton will share some insights from his time spent as Engineering Lead at a large GOV.UK department during most of 2018. There he championed Continuous Delivery practices across 70+ teams and 7 locations, helping to raise standards for software operability, Developer Experience (DevEx), testing, deployments, and inter-team communications. He will share some practical techniques for getting Continuous Delivery working at scale.

Continuous Delivery at scale - Matthew Skelton - NHS Digital agile CoP - Marc...

Matthew Skelton

The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk we explain how and why, based on material from the book Team Topologies by Matthew Skelton and Manuel Pais. From a talk by Matthew Skelton of Conflux at NAV, Oslo on 2020-01-23

Forget monoliths vs microservices - focus on team cognitive load - Team Topol...

Conflux

In this talk, Matthew Skelton (Skelton Thatcher Consulting) explores five practical, tried-and-tested, real-world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT. Logging as a live diagnostics vector with sparse event IDs Operational checklists and 'run book dialogue sheets' as a discovery mechanism for teams Endpoint healthchecks as a way to assess runtime dependencies and complexity Correlation IDs beyond simple HTTP calls Lightweight 'User Personas' as drivers for operational dashboards These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generation and shipping of logs and metrics looks very different from the cloud or 'serverless' case. However, the principles - logging as a live diagnostics vector, event IDs for discovery, etc - work remarkably well across very different technologies. From a talk at Agile in the City Bristol 2017 http://agileinthecity.net/2017/bristol/sessions/index.php?session=44

Practical operability techniques for teams - Matthew Skelton - Agile in the C...

Skelton Thatcher Consulting Ltd

Tendances (19)