Cambios relacionados
Introduce el nombre de una página para ver los cambios en las páginas enlazadas. (Para ver miembros de una categoría, introduce Categoría:Nombre de la categoría). Los cambios realizados en las páginas que tengas en tu lista de seguimiento se resaltarán en negritas.
Lista de abreviaturas:
- N
- Esta edición creó una página (ver también la lista de páginas nuevas)
- m
- Esta es una edición menor
- b
- Esta edición fue realizada por un robot
- (±123)
- El tamaño de la página cambió esta cantidad de bytes
10 sep 2026
|
|
N 13:41 | Agilidad/en 11 cambios historial +4985 [Mberne (11×)] | |||
|
|
13:41 (act | ant) −280 Mberne discusión contribs. (Página creada con «== Agility and AI: a two-way relationship == Generative AI is affecting agility in two directions at once: * '''AI as a tool within agile teams.''' Code assistants, documentation generators, and feedback analyzers are changing the speed and nature of the work. Agility, with its emphasis on continuous adaptation, is the framework best prepared to absorb this shift: it lets the team review its practices at every retrospective as the tools evolve. * '''Agility as a frame…») | ||||
|
|
13:40 (act | ant) −64 Mberne discusión contribs. (Página creada con «* Predictive management assumes it's possible to define the complete product at the start of the project and that deviations from the plan are errors to be corrected. * Evolutionary management—the basis of agility—assumes that knowledge about the product evolves as it's developed, and that adapting the plan to that knowledge is a healthy practice, not a sign of poor planning.») | ||||
|
|
13:40 (act | ant) −68 Mberne discusión contribs. (Página creada con «== Agility versus predictive management == The fundamental distinction between agility and predictive management isn't about speed or tools, but about how uncertainty is managed:») | ||||
|
|
13:40 (act | ant) −75 Mberne discusión contribs. (Página creada con «'''Agility wasn't born from theory but from practice:''' the frameworks that underpin it—Scrum, XP, Crystal, Kanban—were developed by teams looking for more effective ways of working in highly uncertain environments.») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
13:39 (act | ant) −517 Mberne discusión contribs. (Página creada con «== Common mistake == <div class="bok-aviso"> '''Confusing agility with using Scrum.''' Scrum is a specific framework for implementing agile principles, but it's neither the only one nor a definition of agility on its own. A team can use Scrum mechanically and not be agile at all, and a team can be highly agile without following any formal framework. Agility is a way of thinking about work, not a set of ceremonies. </div> == Resources == <div class="bok-recurso"> 📄…») | ||||
|
|
13:37 (act | ant) −57 Mberne discusión contribs. (Página creada con «== References == * Beck, Kent et al. (2001). ''Manifesto for Agile Software Development''. agilemanifesto.org. * Highsmith, Jim. (2002). ''Agile Software Development Ecosystems''. Addison-Wesley.») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
13:37 (act | ant) −26 Mberne discusión contribs. (Página creada con «== See also == <div class="bok-tags"> Agile Manifesto Evolutionary management Predictive management Technical agility Standard Scrum: components and framework Concurrent engineering Special:MyLanguage/AgiLevel|Agi…») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
13:37 (act | ant) −43 Mberne discusión contribs. (Página creada con «<div class="bok-ecosistema"> <div class="texto"> <span class="titulo">'''Want to take your agility further?'''</span> <span class="sub">You can look for upcoming course and exam dates, or go at your own pace by becoming an Agile Club member. Membership includes exclusive resources, e-learning classrooms, and access to [https://scrummanager.com/skillarena/ '''Skill Arena''']: a space to practice and measure your agile skills whenever it suits you.</span> </div> <div cl…») | ||||
|
|
13:37 (act | ant) −86 Mberne discusión contribs. (Página creada con «== Origins and foundations == Agility as a formal movement emerged in 2001 with the publication of the Agile Manifesto, signed by seventeen software development professionals who shared a dissatisfaction with the prevailing management models. Its four values and twelve principles remain the field's conceptual reference, even though how they're applied has evolved considerably since then.») | ||||
|
|
13:36 (act | ant) −182 Mberne discusión contribs. (Página creada con «600px|thumb|center|'''Agilidad'''») | ||||
| N |
|
13:36 (act | ant) +6383 Mberne discusión contribs. (Página creada con «{{Meta-bok|min=5}}») | |||
| 13:09 | Registro de traducción de página Mberne discusión contribs. marcó Agilidad para traducción | ||||
|
|
N 13:00 | Agile Unified Process/en 10 cambios historial +4552 [Mberne (10×)] | |||
|
|
13:00 (act | ant) −164 Mberne discusión contribs. (Página creada con «* For teams working on systems with high architectural complexity, where AUP's emphasis on the elaboration phase remains relevant. * As a bridge for organizations with a RUP culture that want to move toward more agile practices without completely abandoning their process structure.») | ||||
|
|
13:00 (act | ant) −69 Mberne discusión contribs. (Página creada con «# '''Inception:''' the scope and size of the project are identified, an initial architecture is proposed, and the budget is set. # '''Elaboration:''' the suitability of the chosen architecture is confirmed. This is the phase that most distinguishes AUP from other agile frameworks: investing time in validating the architecture before building significantly reduces the risk of having to redo work. # '''Construction:''' incremental development of the system following the…») | ||||
|
|
12:59 (act | ant) −4 Mberne discusión contribs. (Página creada con «== The four phases of the AUP cycle ==») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
12:59 (act | ant) −69 Mberne discusión contribs. (Página creada con «* '''Iterative and incremental:''' development is organized into short iterations that produce partial, working deliveries. * '''Emphasis on architecture:''' the elaboration phase is dedicated to confirming that the chosen architecture is viable before building on it, which reduces early technical risks. * '''Efficient documentation:''' only the necessary documentation is produced, avoiding RUP's documentation overload. * '''Collaboration with stakeholders:''' continu…») | ||||
|
|
12:59 (act | ant) −59 Mberne discusión contribs. (Página creada con «== Context: RUP and its simplification == The Rational Unified Process was a complete but heavyweight software development framework, known for its exhaustive documentation and its tightly defined phase structure. AUP takes its four-phase structure and its emphasis on architecture, but removes much of the documentation bureaucracy and adopts agile practices such as iterative development and continuous collaboration with the customer. == Key characteristics ==») | ||||
|
|
12:59 (act | ant) −84 Mberne discusión contribs. (Página creada con «The '''Agile Unified Process''' (AUP) is a simplified version of the Rational Unified Process (RUP) created by Scott Ambler in the early 2000s. Its aim was to adapt RUP's architectural robustness to agile principles, reducing its documentation overhead and organizing development into short iterations geared toward the continuous delivery of value.») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
12:58 (act | ant) −51 Mberne discusión contribs. (Página creada con «== Common mistake == <div class="bok-aviso"> '''Mistaking AUP for a lightweight agile framework.''' Despite its name and its incorporation of agile principles, AUP is still more structured and documentation-heavy than Scrum or Kanban. Teams looking for real operational agility will find lighter frameworks more useful; AUP makes sense in contexts where architecture and documentation traceability are non-negotiable requirements. </div> == References == * Ambler, Scott W…») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
12:57 (act | ant) −66 Mberne discusión contribs. (Página creada con «== See also == <div class="bok-tags"> Adaptive Software Development Agile Manifesto Evolutionary management Predictive management Methodology map Crystal DSDM </div>») | ||||
|
|
12:57 (act | ant) −43 Mberne discusión contribs. (Página creada con «<div class="bok-ecosistema"> <div class="texto"> <span class="titulo">'''Want to take your agility further?'''</span> <span class="sub">You can look for upcoming course and exam dates, or go at your own pace by becoming an Agile Club member. Membership includes exclusive resources, e-learning classrooms, and access to [https://scrummanager.com/skillarena/ '''Skill Arena''']: a space to practice and measure your agile skills whenever it suits you.</span> </div> <div cl…») | ||||
| N |
|
12:56 (act | ant) +5161 Mberne discusión contribs. (Página creada con «{{Meta-bok|min=4}}») | |||
| 12:45 | Antipatrones difs.hist. +368 TranslateScrum discusión contribs. (Preparación para traducción (Traductor BOK)) | ||||
| 12:45 | Agilidad estructural difs.hist. +306 TranslateScrum discusión contribs. (Preparación para traducción (Traductor BOK)) | ||||
| 12:45 | Agilidad cultural difs.hist. +328 TranslateScrum discusión contribs. (Preparación para traducción (Traductor BOK)) | ||||
| 12:45 | Agilidad difs.hist. +443 TranslateScrum discusión contribs. (Preparación para traducción (Traductor BOK)) | ||||
|
|
N 12:08 | Affinity Mapping/en 10 cambios historial +4729 [Mberne (10×)] | |||
|
|
12:08 (act | ant) 0 Mberne discusión contribs. Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
12:03 (act | ant) −56 Mberne discusión contribs. (Página creada con «Category: Glosario de términos Category:Marcos_y_modelos Category:Prácticas ágiles») | ||||
|
|
12:03 (act | ant) −107 Mberne discusión contribs. (Página creada con «== See also == <div class="bok-tags"> Affinity Estimating Design thinking Brainstorming/Filtering Retrospective How might we Impact mapping </div>») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
12:03 (act | ant) −36 Mberne discusión contribs. (Página creada con «== References == * Kawakita, Jiro. (1967). ''Hassō-hō'' [The abduction method, in Japanese]. Chūōkōron-sha.») | ||||
|
|
12:03 (act | ant) −554 Mberne discusión contribs. (Página creada con «== Common mistake == <div class="bok-aviso"> '''Discussing during the grouping phase.''' When someone explains out loud why they're moving a card to a particular group, they impose their logic on everyone else before the others can form their own. Silence during grouping isn't a formality: it's the mechanism that ensures collective patterns emerge, rather than those of the team's most vocal member. </div>») | ||||
|
|
12:03 (act | ant) −194 Mberne discusión contribs. (Página creada con «<div class="bok-aviso"> The risk is that handing the grouping over to AI removes exactly what's most valuable about the technique: the process of the team forming its own mental connections. The categories that emerge from a human affinity mapping session aren't just a result; they're also a process of cognitive alignment for the team. Using AI as a starting point for discussion is useful; using it to replace the session is not. </div>») | ||||
|
|
12:02 (act | ant) −56 Mberne discusión contribs. (Página creada con «500px|center») | ||||
|
|
12:02 (act | ant) −212 Mberne discusión contribs. (Página creada con «'''Affinity Mapping''', also known as '''Affinity Diagramming''', is a collaborative technique for organizing and categorizing large amounts of ideas, observations, or data into groups based on their similarities or natural connections. It's commonly used in agile project management, UX, and design thinking.») | ||||
|
|
12:02 (act | ant) −115 Mberne discusión contribs. (Página creada con «{{Meta-bok|min=5}}») | ||||
| N |
|
12:02 (act | ant) +6059 Mberne discusión contribs. (Página creada con «Affinity Mapping») | |||
| 12:06 | Adaptive Software Development/en difs.hist. +80 Mberne discusión contribs. | ||||
9 sep 2026
|
|
16:23 | (Registro de traducción de página) [Mberne (3×)] | |||
|
|
16:23 Mberne discusión contribs. marcó Affinity Mapping para traducción | ||||
|
|
16:23 Mberne discusión contribs. marcó Agile Unified Process para traducción | ||||
|
|
16:22 Mberne discusión contribs. marcó Affinity Mapping para traducción | ||||
| 16:20 | Agile Unified Process difs.hist. +296 TranslateScrum discusión contribs. (Preparación para traducción (Traductor BOK)) | ||||
| 16:20 | Affinity Mapping difs.hist. +255 TranslateScrum discusión contribs. (Preparación para traducción (Traductor BOK)) | ||||
|
|
16:19 | Adaptive Software Development/en 8 cambios historial −423 [Mberne (8×)] | |||
|
|
16:19 (act | ant) −37 Mberne discusión contribs. (Página creada con «<div class="bok-ecosistema"> <div class="texto"> <span class="titulo">'''Want to keep learning?'''</span> <span class="sub">In Club Agile you practice and track your progress at your own pace, with exclusive resources, e-learning classrooms, and challenges in Skill Arena. And when you're ready to certify what you know, there are course dates available all year round.</span> </div> <div class="botones"> <div class="bok-btn-outline">[https://scrummanager.com/club/ Club…») | ||||
|
|
16:18 (act | ant) −62 Mberne discusión contribs. (Página creada con «<div class="bok-tags"> Agile Manifesto Extreme Programming Evolutionary management Crystal DSDM FDD Agility Methodology map </div>») Etiquetas: Edición desde móvil Edición vía web móvil | ||||
|
|
16:18 (act | ant) −28 Mberne discusión contribs. (Página creada con «== See also ==») | ||||
|
|
16:18 (act | ant) −57 Mberne discusión contribs. (Página creada con «== References == Highsmith, Jim. * (2000). ''Adaptive Software Development: A Collaborative Approach to Managing Complex Systems''. Dorset House Publishing. * (2002). ''Agile Software Development Ecosystems''. Addison-Wesley.») | ||||
|
|
16:18 (act | ant) −67 Mberne discusión contribs. (Página creada con «<div class="bok-aviso"> '''Treating ASD as a complete operational method.''' Unlike Scrum, ASD doesn't prescribe specific roles, events, or artifacts. It's a conceptual framework that needs to be complemented with specific practices to become operational. Anyone looking for step-by-step instructions will find Scrum or XP more useful; anyone looking for the foundations to understand why agility works will find ASD a valuable read. </div>») | ||||
|
|
16:18 (act | ant) −22 Mberne discusión contribs. (Página creada con «== Common mistake ==») | ||||
|
|
16:18 (act | ant) −80 Mberne discusión contribs. (Página creada con «== ASD and AI product development ==») | ||||
|
|
16:18 (act | ant) −70 Mberne discusión contribs. (Página creada con «ASD isn't a commonly adopted framework in 2025, and it has largely been absorbed by Scrum and other agile approaches that took up its principles in more concrete, operational ways. Its value today is mainly conceptual:») | ||||