Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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:

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