Remove Agile Remove Development Remove Document Remove Weak Development Team
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 97
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
Insiders

Sign Up for our Newsletter

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

article thumbnail

Your Ultimate Guide to Agile Transformation

Agile Velocity

Agile has been shown to shorten time-to-market, increase quality, instill predictability, improve customer satisfaction, and create an overall happier working culture. Agile Transformation involves all levels of the organization and applies Lean-Agile principles to business processes, practices, tools, operations, and culture.

Agile 59
article thumbnail

Nine Agile Antipatterns That Lead To Disaster

The Product Coalition

Agile antipatterns or scrum antipatterns are (poor) practices that are utilized to enhance a process. Nonetheless, they impede your efforts and slow your progress towards attaining Agile objectives, thereby achieving the opposite effect. List of destructive agile antipatterns and how to avoid them 1.

Agile 115
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.

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

The Differences, Pros and Cons Between Waterfall and Agile Methodologies

The Product Coalition

At the beginning of any software development project, managers think of which methodology is between waterfall and agile. It’s essential to follow clearly defined processes or software development life cycle (SDLC) to ensure software development quality. Waterfall and agile: A smart method or bad solution?