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:

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