article thumbnail

5 signs your agile practices will lead to digital disaster

CIO

Business leaders expect IT to develop new products, improve customer experiences, automate workflows, and deliver new artificial intelligence capabilities. Many IT teams use agile methodologies to iteratively deliver feature-rich releases, improve capabilities, address technical debt, and experiment with emerging technologies.

Agile 338
article thumbnail

Lessons Learned in Product Development from Paulo Neto’s eMLS Success

Perficient

Our colleagues in Atlanta had the wonderful opportunity to step into the world of competitive gaming as they met, and even got to play against multiple eMLS champion Paulo Neto! Like eGaming, success in product development requires a holistic approach, combining innovation, flexibility, and a relentless pursuit of excellence.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Agile Book Club: Team Dynamics

James Shore

Team dynamics form the bedrock of Agile teams’ ability to develop and deliver software. They’re the invisible undercurrents that determine your team’s culture. In this session, Diana Larsen and Linda Rising help us explore the dynamics that make and break Agile teams. Team Dynamics. ??

article thumbnail

Why 47% of Agile Transformations Fail!

scruminc

My talk on “Why 47% of Agile Transformations Fail!” My slides are posted here - Why 47% of Agile Transformations Fail. A recent Forbes survey indicated to me that about 47% of Agile Transformations fail and 77% of Agile Transformations are Scrum transformations so most of the failures are due to bad Scrum.

Agile 124
article thumbnail

How to Sweeten a Bitter Manager, a Micromanagement Survival Guide

Xebia

Are you a developer who has to put up with a bitter manager? A Product Owner who feels like they’re being sucked dry by an overbearing Agile coach? Or maybe a manager, leader, or coach who wants to understand how to support their team better? Mostly though, it is demotivating and, therefore, bad.

How To 147
article thumbnail

Bliki: OutcomeOverOutput

Martin Fowler

Imagine a team writing software for a shopping website. If we look at the team's output, we might consider how many new features they produced in the last quarter, or a cross-functional measure such as a reduction in page load time. Lines of code are a useless measure even if they weren't so easily gamed.

article thumbnail

Agile Retrospectives

Agile Pain Relief Notes from a Tool User

The goal of this post is to give teams a solid introduction on how to have not-sucky Sprint Retrospectives. Retrospectives are explicitly part of Scrum – “ The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.” It’s Not a Post-Mortem.

Agile 90