Remove Agile Remove Development Remove Software Development Remove Weak Development Team
article thumbnail

Dealing with an Underperforming Development Team

Roman Pichler

What is Bad Performance? Before I discuss how you can help an underachieving team, let’s briefly explore what good performance looks like, assuming that an agile, Scrum-based process is used. Second, the team participates in continuous discovery and strategizing , and its members regularly help refine the product backlog.

article thumbnail

How to Become an Amazing Agile Developer

The Product HQ

Wondering what it takes to become an amazing agile developer? This post outlines all the traits, essential skills, and soft skills that characterize what it means to be an amazing agile developer. 8 Steps to Become a Rockstar Agile Developer Here is a step-by-step process on how to become an agile developer: 1.

Agile 52
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

Why designers fail to integrate into Agile teams

UX Planet

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. Desperate to find an alternative to our ineffective process, I stumbled upon Agile and it blew my mind. But it wasn’t all that bad.

Agile 84
article thumbnail

How Agile Has Changed Product Management

Roman Pichler

Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager. The Brave New Agile World.

Agile 248
article thumbnail

Timeline of 20 Common Product Development Activities

The Product Coalition

How long an activity takes can have a huge impact on success or the perception of success when developing products. More often than not, teams are overly optimistic on the timeline that will be required to complete an activity. You can put unnecessary pressure on your team. You might design your organisation or team poorly.

article thumbnail

How Agile Has Changed Product Management

Roman Pichler

Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager. The Brave New Agile World.

Agile 156
article thumbnail

8 Tips for Collaborating with Development Teams

Roman Pichler

Manage the Product, not the Team. Focus on your job as the product manager or product owner, and manage the product, not the team. Treat the Team as an Equal Partner. The team members are not your resources but the people who create your product. Assume that the team members want to do their best.