article thumbnail

Asana vs. ClickUp: In-Depth Comparison

ProjectManager.com

Certainly, Asana is simple to use and pleasing to the eyes, while ClickUp is similar to Asana, but with software development tools. ClickUp battle for project management software supremacy, is ClickUp. ClickUp was founded in 2016 by Zeb Evans and Alex Yurkowski and is headquartered in San Diego, California.

article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Scrum.org

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). “The Controls, deliverables, artifacts.

2010 232
Insiders

Sign Up for our Newsletter

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

article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

This effect has been observed with flight crews (Orasuna, 1990), nuclear plant control crews (Waller, Gupta & Giambatista, 2004), and work teams (Urban et. This is not because team members have developed telepathy, but because they have learned so well what is expected of each other that they don’t need to communicate about that anymore.

2004 237
article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Gunther Verheyen

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141
article thumbnail

How to shrink your project with the Minimum Viable Product: 5 Tips for Minimum Viable Projects

Inloox

The Minimum Viable Product concept , which we know from product development, meets precisely this challenge. In software development, for example, a Minimum Viable Product helps to minimize the number of feature requests to a feasible level. Allow your team to make decisions: This requires courage and a positive image of people.

Lean 130
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

This requires highly controlled experiments where only the level of agility is manipulated in a team. Several empirical studies have indeed found that teams with a frequent delivery strategy are more likely to deliver successful project outcomes and satisfy stakeholders than teams that do not ( Chow & Cao, 2008 , Jørgensen, 2016 ).

Agile 213
article thumbnail

Fika Stories 1 – Help! Our Kanban Died!

Digite

In this 2-part series, we are honored to publish a couple of blog posts by (2016 Brickell Key award winner) Christophe Achouiantz, Kanban thought-leader, consultant and coach. This article was originally published on Lean-Agile Software Development blog and can be found here– [link]. Now, Good luck!

Lean 79