How to Get the Best of Artificial Intelligence (AI) with Lean/Agile?

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

During the last few years, we have seen that nearly all technology based products and services must learn to leverage AI in order to compete effectively in the marketplace. We recommend adopting Lean/Agile principles and practices for this purpose. In this manner, organizations can continuously improve time to market and realize exceptional value early and often. In this post we’ll describe the top challenges that we see in the field as well as tips and tricks for applying Agile to get the best of AI. These are all patterns that we’ve applied successfully at AgileSparks in our work with a diverse set of clients. What are the top challenges that we’ve seen in the field regarding AI in the organization?

  • Working as a silo separated from the rest of the teams, often feeling that their role in the product development is not clear (“you don’t understand the nature of our work”, “we have to research a long time before you can start”, etc.).
  • Lack of alignment between the AI work and the rest of the organization due to separate goals & backlogs.
  • Lower engagement of the AI people with the rest of the people in the organization.
  • Infrequent feedback and learning due to working with big requirements / long research.
  • Lack of transparency regarding the AI work – not clear what is being worked on and how it is progressing.
  • Not sufficiently leveraging the AI group abilities due to low and late involvement of the AI group in the backlog refinement.

Why is it important to address the above patterns? The above challenges contribute to inefficiencies in the flow of value in the organization due to delays and waste in the work. In this post, we’re going to discuss how to incorporate AI people and work within the product development life cycle in order to overcome these deficiencies. We will differentiate between Data Scientist (aka Algorithm Developers) and Data Analyst roles. Note that in some organizations these roles are done by the same people. How should Data Scientists collaborate within the life cycle of product development? We’ll start first with the Data Scientists. Data Scientists write algorithms and build statistical models. They arrange sets of data using multiple tools in parallel and build automation systems and frameworks. We’ve found that the following approaches help Data Scientists to better collaborate with the rest of the organization throughout the business & product development lifecycle:

  • The lead Data Scientist in the organization participates in defining the vision & roadmap.
  • Data Scientists are members of the Program level (multiple teams working in collaboration) and participate in the Program events.
  • Data Scientists are part of the backlog refinement process.
  • The Data Scientists’ research & business features should be sliced smartly (vertically instead of horizontally) to achieve small valuable batches that will be continuously integrated and feedbacked. The small batches might be actual working models or validated learning that indicates whether we’re hearing in the right direction or not.
  • Data Scientists collaborate with each other in a dedicated Agile Team leveraging Lean/Agile mindset and practices (similarly to other Agile Teams) and sharing the same synchronization and cadence as other Agile teams.
  • Member of the AI Community of Practice (CoP)

How should Data Analysts collaborate within the life cycle of product development? Data Analysts design and maintain data systems and databases, using statistical tools to interpret data sets, and prepare reports to present trends, patterns, and predictions based on relevant findings. At AgileSparks we’ve found that the following approaches help Data Analysts to better collaborate with the rest of the organization throughout the business & product development lifecycle:

  • Data Analysts are part of the backlog refining process to ensure that data considerations are discussed and applied for all backlog items.
  • Most of the Data Analysts work is part of the functional features included in the user stories that are implemented by the team.
  • Data Analysts are members of the development Agile teams, sharing the same goals and backlog. They participate as full Agile team members.
  • Member of the AI Community of Practice (CoP).

Summary From our experience, by implementing the above approaches, organizations will gain the following benefits:

  • The AI group will be aligned with the business purpose.
  • The AI group will become more engaged with the purpose and work of the rest of the organization.
  • The organization and the AI group will gain transparency regarding the AI work and progress.
  • The AI group will be more effective and efficient bringing real value faster by working with small valuable batches and continuously learning & improving.
Subscribe for Email Updates:

Categories:

Tags:

An Appreciative Retrospective
Professional Scrum Master
Enterprise DevOps
Release Train Engineer
Acceptance Test-Driven Development
Value Streams
ScrumMaster Tales
Entrepreneurial Operating System®
Elastic Leadership
Scrum.org
Built-In Quality
Video
Certified SAFe
ART Success
Coaching Agile Teams
Slides
Applying Agile Methodology
Managing Projects
Agile Testing Practices
Systems Thinking
predictability
Professional Scrum with Kanban
Software Development
Sprint Retrospectives
Agile Israel Events
Kaizen
Large Scale Scrum
Implementing SAFe
ARTs
ALM Tools
LPM
Agile Program
AI Artificial Intelligence
Program Increment
Scrum Master
Introduction to Test Driven Development
Agile Marketing
Keith Sawyer
PI Objectives
Continuous Deployment
Jira admin
AgileSparks
Daily Scrum
Self-organization
ATDD
Frameworks
speed at scale
Agile Games
lean agile change management
Product Ownership
Risk Management in Kanban
Kanban Basics
Professional Scrum Product Owner
Agile India
Planning
Kanban Kickstart Example
Portfolio for Jira
SAFe
Agile Mindset
Sprint Planning
Agility
Agile and DevOps Journey
Risk Management on Agile Projects
The Kanban Method
Certification
Jira
Agile Techniques
Test Driven Development
Kanban Game
Agile Project Management
AI
Lean Agile Basics
Nexus
A Kanban System for Software Engineering
Agile Development
Kaizen Workshop
ROI
System Archetypes
Reading List
Agile Exercises
Rovo
Jira Cloud
Continuous Improvement
Managing Risk on Agile Projects
Continuous Integration
Scrum Values
System Integration Environments
Atlaassian
PI Planning
Kanban 101
Lean and Agile Techniques
Lean Startup
Team Flow
WIP
Scrum Master Role
Advanced Roadmaps
Presentation
Continuous Delivery
Agile in the Enterprise
chatgpt
SPC
Agile Contracts Best Practices
User stories
DevOps
Hybrid Work
Lean and Agile Principles and Practices
Principles of Lean-Agile Leadership
Scrum With Kanban
Agile
Retrospectives
Webinar
Development Value Streams
Effective Agile Retrospectives
Atlassian
Spotify
Scrum
Rapid RTC
Agile Assembly Architecture
Agile Product Ownership
Lean Software Development
Nexus vs SAFe
Kanban
SA
System Team
Perfection Game
Lean Budgeting
Agile Release Management
Agile Delivery
Code
Pomodoro Technique
Lean Agile Organization
Scrum Primer
Agile Risk Management
Achieve Business Agility
Implementation of Lean and Agile
BDD
SAFe Release Planning
transformation
RSA
Agile for Embedded Systems
What Is Kanban
ATDD vs. BDD
Legacy Code
The Agile Coach
Continuous Planning
Business Agility
Agile Israel
Lean Agile
Agile Project
Covid19
Manage Budget Creation
Change Management
TDD
agileisrael
EOS®
Agile Basics
Scaled Agile Framework
Iterative Incremental Development
SAFe DevOps
Jira Plans
Tools
Legacy Enterprise
Agile Community
Introduction to ATDD
Scrum Guide
Agile Outsourcing
Quality Assurance
IT Operations
Software Development Estimation
Nexus and SAFe
speed @ scale
LeSS
Accelerate Value Delivery At Scale
Releases Using Lean
Games and Exercises
Tips
Agile Release Planning
Lean Agile Management
QA
Process Improvement
RTE Role
Risk-aware Product Development
LAB
Nexus Integration Team
Scrum and XP
GanttBan
NIT
Confluence
Lean-Agile Budgeting
Limiting Work in Progress
RTE
Product Management
Lean-Agile Software Development
Story Slicing
Engineering Practices
Artificial Intelligence
Operational Value Stream
POPM
Nexus and Kanban
Sprint Iteration
Lean Agile Leadership
Agile Product Development
Lean Risk Management
Amdocs
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart