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:

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