Methodologies / Methodos
People
Keys
Ceremonies
Various
100

Is defined as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology,

and the requirements for business success.” Thus, the method focuses on three main elements of a product or solution: people, technology, and business.




Design Thinking

100

Is a self-organized team (ideally max. 10 members) including externals delivering a product or a set of products.

The Internal Business Partners set the priority, based on this, the product owner prioritizes the backlog.

Squad

100

Process through items are reviewed by the Squad and revised, providing more detail and ensuring that there is greater clarity in the requirements for that item.

Should be an ongoing process

Backlog

100

This is a time-boxed event of 3 hours, or less, and for squad using scrum it is to end a Sprint or Iteration.

It serves for the Squad (or scrum team) to inspect the past Sprint and plan for improvements to be enacted during the next Sprint.

Retrospective

100

@ BASF, is part of the BASF Project Management Framework

(BPMF).

PLC

200

This method is a means to design, manage, and improve flow systems for knowledge work.

Also allows organizations to start with their existing workflow and drive evolutionary change.

They can do this by visualizing their flow of work, limit work in progress (WIP) and stop starting and start finishing.

KANBAN

200

A collection of squads around a stable purpose is a ______.

It is defined either by the structure of our internal delivery or, which is more likely, by the IBP centric view.

Tribe

200

It is an informal, natural language description of one or more features of a software system or anything else that is creating value for the customer when they are delivered.

Are often written from the perspective of an end user.

User Story

200

A team planning meeting, held at the start of each sprint, that determines the work that is to be done in the coming sprint.

Sprint Planning

200

Palabra que aprendimos hoy

multitasstin

300

Es galán de nevería y tiene risa contagiosa

Ricardo

300

Is the sole person responsible for managing the Product Backlog and takes care of the prioritization.

Maximize the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Squad(s) (or Scrum Team(s).

Product Owner

300

Is a list of tasks identified by the Scrum team to be completed during the Scrum sprint.

During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story.

Sprint Backlog

300

Daily meeting of around 15 minutes for the team to synchronize on the activities they are working on.

Daily stand-up

300

Is an incredibly useful technique when working on projects where the agile development method is used. Is focused on the experience under design and is less focused on deliverables than traditional UX. It requires a greater level of collaboration with the entire team. The core objective is to focus on obtaining feedback as early as possible so that it can be used to make quick decisions.

LeanUX

400

The _______ model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards through the phases of conception, initiation, analysis, design, construction, testing, production / implementation, and maintenance.

Waterfall

400

Consists of a Product Owner, DevOps Engineers, and a Scrum Master (or Agility Master).

Scrum Team

400

Is a process framework used to manage product development and other knowledge work.

Is empirical in that it provides a means for teams to establish a hypothesis of how they think something works, try it out, reflect on the experience, and make the appropriate adjustments.

Sprint

400

A meeting where the team demonstrates the functionality added during the sprint. The goal is to obtain feedback from the stakeholders invited to the sprint review.

Sprint review

400

contains:

- Objective for the next 3 months

- Ambitious key results, which should to be achieved (80%)

- 4 weeks activities

- Individual weekly priorities

- Health check



OKR

500

t is a lightweight process framework for agile development, and the most widely-used one. 

It is about collaborating and communicating both with the people who are doing the work and the people who need the work done. 

It is about delivering early and often, responding to feedback and increasing business value by ensuring that customers get what they actually want.

SCRUM

500

Es buena organizadora de eventos, la planeación es lo suyo.

Ale Valadez

500

Tiene empuje, buena vibra y unos brazotes

Daniel

500

acklog items are reviewed by the Squad and revised, providing more detail and ensuring that there is greater clarity in the requirements for that item.

Backlog Refinement

500

Dice muy bonito Shile Shilaca Osho Oshenta

Zalia