Agile and documentation - Scrum.org
2018年1月3日 · Jason Pearce, your documentation efforts should focus on what is needed and adds value to the customer.For example if you develop a software and it is wise to add documentation that answers users most FAQ therefore reducing the Total cost of ownership (TCO) it is an important piece and ideally should be included in the Acceptance criteria of that PBI !
The Agile Manifesto - Scrum.org
Created by 17 visionaries in 2001 including Scrum.org founder and chairman Ken Schwaber who co-created Scrum, the Agile Manifesto was developed to look at the core principles and values for Agile software development.
How to live the 4 values in the Agile Manifesto - Scrum.org
2022年2月17日 · The Agile Manifesto (penned in 2001) includes four values and 12 principles that describe a new approach to complex work. Agile is an umbrella term comprising a variety of frameworks and approaches to value delivery, including Scrum. Previously, we discussed the 12 principles included in the Agile Manifesto and how they play out in the real world. This week, we turn our attention to each of ...
Agile Principles - Effective Communication - Scrum.org
2023年3月31日 · When the Agile Manifesto was created, the only way to carry out face-to-face communication was to be physically together. Zoom, Teams and other forms of easily accessible video conferencing tools did not yet exist. Today we can have face-to-face conversations without being colocated. The Agile Manifesto authors would not have made the distinction.
Documentation in Agile, how should it be handled? - Scrum.org
2018年10月3日 · It's important to understand that Agile is not a noun, nor a methodology, nor a framework. You can be agile, but you can't do Agile. The manifesto for agile software development (commonly called the agile manifesto) is a short collection of values, and is based on twelve principles. Indeed, according to the manifesto:
The Agile Values in Practice - Scrum.org
2019年4月1日 · Documentation likely needs to be created in order to be releasable. This documentation could be part of the team’s process (e.g. keeping an architecture diagram up-to-date), the automated tests to maintain quality, or it could be something that is used by customers and have a specific value associated with it (e.g. product training video).
How the 12 principles in the Agile Manifesto work in real life
2022年2月9日 · The Scrum framework comes with its own guardrails and values, but it is worth taking a moment to consider the base upon which Scrum is founded by examining the principles and values of the Agile Manifesto. The Agile Manifesto includes four values and 12 principles that describe a better way to approach complex work. In this article, we will discuss each of the 12 principles and what they mean ...
Risk Mitigation: Agile Usable Products vs Documentation in …
2023年7月20日 · 🎯#Agile Usable Products vs. Documentation in Traditional Project Management📝 💡Are you still torn between embracing Agile's nimble strides or holding onto the tried-and-true documentation-heavy Traditional Project Management? Let's crack the code! 🕵️♂️ In an ever-evolving software development landscape, striking the right balance is pivotal.🔧 Agile’s focus on ...
Gross Definitions: 144 Agile Terms You Simply Have To Know
2017年3月17日 · Anti-pattern: A behavioural or organisational pattern or practice which is contrary to an agile way of working, and which suggests the need for more appropriate patterns or practices. Artefact: An input or output of an agile process. In Scrum there are three artefacts: the Sprint Increment, the Sprint Backlog, and the Product Backlog.
ITIL and Scrum | Scrum.org
2018年3月24日 · I was wondering how people in a heavy ITIL environment manage to be agile. For me, agile is about small, autonomous units getting 'stuff done' with the minimal amount of documentation. ITIL seems hot on process and documentation and many 'managers' (service manager, delivery manager, demand manager and so forth). Any thoughts, guys?
跳至内容