Remove 2001 Remove Article Remove Software Developers Remove Weak Development Team
article thumbnail

Deconstructing Being Agile

The Product Coalition

Agile vs. Being Agile Agile became popular shortly after ‘The Agile Software Development Manifesto ’ was published in 2001. Blindly adopting Agile is not a guarantee that a team will be agile , as these additional Agile rules are not essential to being agile. This is why one-size-fits-all Agile solutions are a bad idea.

Agile 104
article thumbnail

Agile at Scale – Outcome Driven (or Broken)

Tyner Blain

Taking agile, a process otherwise optimized for small, cross-functional, collaborative teams and making it work at scale is fascinating. Think of a couple dozen teams (a couple hundred people) working to deliver across a couple hundred systems, for a multi-billion dollar organization. Getting Faster at Building the Wrong Thing.

Agile 150
Insiders

Sign Up for our Newsletter

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

article thumbnail

The Collision of Product Management and Product Ownership

The Product Coalition

Scrum came about even earlier than the agile manifesto almost a whole decade to be exact (although you can traces origins earlier back to 1986 with the article The New New Product Development Game ). In fact they decided to broaden the scope of the role by bringing it closer to the team and customers?—?this

article thumbnail

The Many Flavors Of Agile: What’s The Right One For Your Team? | Bethany Pagels-Minor, Apple | BoS USA 2018

Business of Software Conference

Agile methodology sounds confusing and difficult, but Bethany Pagels-Minor breaks it down to bite-size slices of delicious cakes that will will help every team work better, communicate better, and provide better returns. from Business of Software Conference. Bethany Pagels-Minor, Apple. Unsubscribe anytime. Transcript.

Agile 61
article thumbnail

The Evolution of Modern Product Discovery

Product Talk

Instead, product teams are experimenting their way to viable solutions. We are putting our customers first, taking the time to discover unmet needs, and developing solutions that address those needs. into context and help product teams know what to use when. We no longer take months or years to release value to our customers.