AgileBlackBelt - Learn web development - Web development lessons for beginners

"Agile is to projects what oil is to engines!" — Carlos Cheimak

Agile as a Mindset

Agile is not just something you do. It is something you become: a way-of-thinking, a mindset, a philosophy and an art to perform and perfect. The art of delivering amazing value quickly, flexibly, with minimum waste and while continuously improving and learning.

To fully enjoy agile as a whole it is good to understand its parts fully and deeply.

Our goal is to collect, select and offer the quintessential best ("Black Belt") explanations about each aspect of Agile, so that anyone interested can access the best distilled wealth of Agile knowledge and contact each other for mutual advice. If you don't know how or who to contact you can contact us.

In the following pages we explore, clarify, show and share the best sources we were able to select, that explain each concept: please suggest better/other sources and share your ideas through us with the community.

Pillars of Agile: 3 Roles - 1 of 3

Vision & Decision: the Product Owner

The Scrum Guide in scrumguides.org states the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

The Product Owner is also accountable for effective Product Backlog management, which includes:

* Developing and explicitly communicating the Product Goal;

* Creating and clearly communicating Product Backlog items;

* Ordering Product Backlog items; and,

* Ensuring that the Product Backlog is transparent, visible and understood.

The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.

For Product Owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review.

The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.

Pillars of Agile: 3 Roles - 2 of 3

Teacher and referee: The Scrum Master

The Scrum Guide in scrumguides.org states the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.

Scrum Masters are true leaders who serve the Scrum Team and the larger organization.

The Scrum Master serves the Scrum Team in several ways, including:

Coaching the team members in self-management and cross-functionality;
Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done;
Causing the removal of impediments to the Scrum Team’s progress; and,
Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.

The Scrum Master serves the Product Owner in several ways, including:

Helping find techniques for effective Product Goal definition and Product Backlog management;
Helping the Scrum Team understand the need for clear and concise Product Backlog items;
Helping establish empirical product planning for a complex environment; and,
Facilitating stakeholder collaboration as requested or needed.

The Scrum Master serves the organization in several ways, including:

Leading, training, and coaching the organization in its Scrum adoption;
Planning and advising Scrum implementations within the organization;
Helping employees and stakeholders understand and enact an empirical approach for complex work; and,
Removing barriers between stakeholders and Scrum Teams.

Pillars of Agile: 3 Roles - 3 of 3

Self-organizing and cross-disciplined: The DevTeam

Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.

The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:

Creating a plan for the Sprint, the Sprint Backlog;
Instilling quality by adhering to a Definition of Done;
Adapting their plan each day toward the Sprint Goal; and,
Holding each other accountable as professionals.

(in construction)

(in construction)

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Ask for help, offer help!

Can anyone participate?

There are no prerequisites to participating except being very passionate about developing software.

Is there a cost?

Money should not stop anyone from asking or answering if someone needs help: We appreciate talented, curious, creative, determined, motivated people. 😊

If you are creative, determined and would like to share your experience or knowledge or simply ask, then let's talk.

Carlos

Contact Us






Captcha: 17 + 1 - 1 =