Remove 2013 Remove Blog Remove Development Team Review Remove Software Development
article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. Scrum is part of agile software development and teams practicing agile. What Is the Scrum Methodology?

SCRUM 332
article thumbnail

A Review Of Scrum For Kanban Teams

Digite

In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. First off, I have to say that I’m not 100% certain how I feel about Yuval’s blog post. What will I do today to help the Development Team meet the Sprint Goal? Disclaimer.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Beginner’s Guide to Kanban for Agile Marketing

Digite

We’re honored to republish this blog post ‘Beginner’s Guide to Kanban for Agile Marketing’ by Andrea Fryrear which was originally published in the Agile Sherpas blog! But, for teams that chafe under the strictures of the Scrum process, Kanban can be a freeing alternative. Creating Your First Kanban Board.

Agile 110
article thumbnail

Team Management: The Key of to Success

International Institute for Learning

For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams. If it takes more than two pizzas to feed (with a slice) the team, the team is likely too big.

article thumbnail

30 Simpler Asana Alternatives For Creative Teams

Teamweek

While creative teams need to still deliver on time and within budget, they thrive by keeping an eye on the ‘big picture’ The project management tool you use for your creative team needs to do just that. That means, allowing your team to get things done without feeling overwhelmed or micro-managed. Ease of use.