article thumbnail

Can you be agile if you release only once a year?

Scrum.org

( Japanese version・日本語版 ) When picturing an effective and truly agile product development team, one often imagines a software development team, pushing some software to production every day, maybe multiple times a day, ala Amazon. But most teams that try it find out that the benefits exceed the costs.

Agile 170
article thumbnail

Newbies’ Guide to Scrum Project Management 101

nTask

Anyhow, this case study illustrates different real life examples of Scrum Project Management. The term Agile refers to a way of managing projects that incorporates constant improvement, scope flexibility, team involvement, and delivering crucial quality products. These teams need to be adaptive to change and highly flexible.

SCRUM 132
Insiders

Sign Up for our Newsletter

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

article thumbnail

Team Management: The Key of to Success

International Institute for Learning

According to a common and general definition, Team Management can be seen as the ability of an individual (manager) or of an organization to lead a group of people to accomplishing a task or common goal. Good management of a team means to do the best by and for the employees. By Luigi Morsa.

article thumbnail

Crossing the client–developer divide: 5 best practices for building a better client relationship

Planio

Crossing the client/developer divide: How to build transparency with better customer communication and the right tools. Putting it all together: A client relationship-building case study from day one. Client/developer transparency breeds the kind of trust that turns one-off projects into long-term relationships.

article thumbnail

In-Depth: The Science On Sustainable Pace, Stress, And Motivation

Scrum.org

How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.

article thumbnail

Government Lessons in People Over Process

Leading Answers

My first opportunity to create and run a large agile team did not start well. Having had good successes with small to medium sized agile teams I was keen to unleash the benefits on a bigger scale. A clean-sheet development opportunity with a smart team and engaged business group – what could go wrong?

article thumbnail

The art of unshipping: How to deprioritize features, phase out projects and sunset products

Planio

Evernote: A case study on how complexity kills products. Unshipping is a term coined by the team at Mixpanel to describe removing a feature or product that is already live to users. Product teams become unnaturally attached to their product roadmaps. Developers and product teams are almost always focused on more.