Blog

Agile Mindset

No QA? All QA!

One of the major topics that intimidate test engineers is the No-QA question or approach (depending on your view of it).

I heard such responses after the session “Fiverr delivering fast..No QA”, by Gil Wasserman, Fiverr VP R&D, at our Agile Israel 2016 event. QA members asked me if they should look for their next role, and I keep hearing this concern whenever this topic arises.

So, is it true? Should we eliminate the QA role? Or better say – merge it into the developer’s role?

Agile Transformation

Agile Transformation at WilliamHill Case Study

AgileSparks Provides a Successful Agile Transformation at William HillIndustryEntertainment, Betting, and GamingSolutionCross functional Product Dev cells, working in Scrum and KanbanResults

Productivity Increased – Moving from delivering 1 application per month to 10 in a quarter
Significant quality increase – Number of rollbacks reduced
A better starting point, focusing on unique developments that serve the business
Teams satisfaction increased

Agile Leadership

Agile Release Train Leadership Team – Servant Leadership In Action During PI Planning

Last week I helped facilitate Program Increment (PI) Planning for an Agile Release Train (ART) practicing the Scaled Agile Framework (SAFe). One impediment for this ART was that although the leadership team ROAMed risks in PI Planning as well as continued to manage the flow of risks/issues using a ROAMing Kanban Board throughout PI execution, there wasn’t enough clarity and alignment around what exactly would Owning a risk look like and what are the expected deliverables/objectives.

Agile Mindset

“Wake up in the morning” Game

A Quick Fun Way to Understand the Basic Concept of Iterative Incremental Development A fundamental aspect of Agility is incremental and iterative development. It’s so

Agile Mindset

How To Keep Development Scope From Growing Wild

A big problem with a garden is that it doesn’t stop growing. And so does the scope of a software development project.

A lot of effort is invested by gardeners in fighting the growing garden. They are constantly weeding, pruning, and trimming to control how the garden looks and to make sure it best serves its purpose.

How much are you investing in weeding your scope?

Change Management

Invitation-Based SAFe Implementation – a SAFe Guidance Article

Invitation and Pull-based approaches for implementing agile at scale have been a reoccurring theme in my work, writing, and talks in recent years – including

Agile

Lean Agile Depth Assessment – Assessing your Agile Maturity

How to use:

Gather your team
Go through the scan and score what you are doing and what not.
Figure out what you want to try next that will improve your capabilities in the relevant direction.

Agile Marketing

Are we there yet? Assessing Agile Marketing Maturity

In a recent Agile Marketing Meetup in Boston we tried to figure out how mature are the Agile Marketing teams/organizations out there. Last week I helped facilitate a third quarterly Agile planning event (also known as SAFe PI Planning or Big Room Planning) for a group of agile marketers I’ve been working with for the past year. This was a good opportunity to ask this question.

Agile Leadership

The “Manager’s Card”

There is nothing like a good long run for clear thinking and giving rise to new ideas. This post is a result of my weekend run, and it’s about managers and why it is so hard to impact their mindset in the Agile journey.

The idea originated as a result of my experience working with this company where the managers find it extremely difficult to relate to the newly formed scrum teams and instead keep communicating with their original teams (Dev and QA teams) and at the same time keep complaining about how the “scrum teams” are not accountable for their end-to-end deliveries.

Agile Mindset

The Critical Difference Between Backlog and To Do (Kanban, Scrum)

When we build a kanban board to manage our work (either practicing Kanban or Scrum) we usually create a Backlog list (usually the first column) and a To Do list (following the Backlog). I’ve noticed that many times the separation between the two is artificial and people don’t always understand the critical difference between the two. I’d like to discuss it here.

Subscribe for Email Updates:

Most New:

Categories:

Agile

Agile Estimations

Agile Games

Agile Israel

Agile KPIs

Agile Leadership

Agile Marketing

Agile Metrics

Agile Mindset

Agile Testing

Agile Tools

Agile Transformation

AI - Artificial Intelligence

Atlassian

BDD

Breadth – Going Wider Toward Business Agility

Build in Quality

Business Agility

Case Studies

Change Management

Confluence

Continuous Deployment

DevOps

Engineering Practices

EOS and Agile

Events

Events & Webinars

Facilitation

Feature teams

Flow

Getting Started

Improving – Going Deeper/better

Insights

Jira

Kanban

Lean Kanban

Lean Portfolio Management

Lean Startup

Nexus

OKRs

Organizational Agility

Per-Topic Reading Lists

Presentations

Product Management

Product Ownership

Project Management

Rovo

Scaled Agile Framework

Scaling – Going Deeper

Scaling Agile

Scrum

Scrum with Kanban

TDD

Teamwork

The AgileSparks Way

Thought Leadership

Unit Tests

Videos

Webinars

Tags:

Applying Agile Methodology

SAFe Release Planning

GanttBan

Introduction to ATDD

Atlassian

AI Artificial Intelligence

ROI

Risk Management in Kanban

Planning

Kaizen

Agile Games and Exercises

Scrum Values

Scrum Master

Quality Assurance

Lean Budgeting

Jira Cloud