2001 Framework Leadership Weak Development Team 
UX Planet
FEBRUARY 13, 2024
Prescriptive Agile frameworks make it hard for designers to add valuable contributions to the team. I designed every detail in Photoshop before handing the mockups to the developers. I was excited to be part of a cross-functional team and I could not wait to start working in sprints. But it wasn’t all that bad.
Atlassian
FEBRUARY 28, 2022
Creating a strong, cohesive team takes intention and planning. Researchers have been studying team dynamics for decades. There’s a significant body of knowledge about which organizational structures provide the best results given the circumstances, goals, and personalities involved in a team. 5-second summary.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The Product Coalition
AUGUST 27, 2018
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.
The Product Coalition
MAY 15, 2019
The agile manifesto turned eighteen this year, the Scrum framework is even older?—?have 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 ). are they one role, two roles?
Business of Software Conference
DECEMBER 11, 2019
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. It’s called ‘the many flavors of agile and what’s the right one for your team?’ Unsubscribe anytime.
Expert insights. Personalized for you.
84 
Let's personalize your content