Editing Agile software development (section)

===Efficient and face-to-face communication===
The 6th principle of the agile manifesto for software development states "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation". The manifesto, written in 2001 when video conferencing was not widely used, states this in relation to the communication of information, not necessarily that a team should be co-located.

The principle of [[Colocation (business)|co-location]] is that co-workers on the same team should be situated together to better establish the identity as a team and to improve communication.<ref>{{cite web |url=https://www.infoq.com/news/collaborative-team-space-study |title=Study: Co-Located Teams vs. the Cubicle Farm |last=Preuss |first=Deborah Hartmann |date=13 October 2006 |website=InfoQ |access-date=2018-10-23}}</ref> This enables [[face-to-face interaction]], ideally in front of a whiteboard, that reduces the cycle time typically taken when questions and answers are mediated through phone, [[Persistent Chat|persistent chat]], wiki, or email.<ref>{{cite web |url=https://www.pearson.com/us/higher-education/program/Cockburn-Agile-Software-Development-The-Cooperative-Game-2nd-Edition/PGM38838.html |title=Agile Software Development: The Cooperative Game |last=Cockburn |first=Alistair |date=2007 |website=www.pearson.com |publisher=Addison-Wesley Professional |language=en |access-date=2018-10-23 |edition=2nd}}</ref> With the widespread adoption of remote working during the COVID-19 pandemic and changes to tooling, more studies have been conducted<ref>{{cite web | url=https://www.managers.org.uk/knowledge-and-insights/research-thought-leadership/management-transformed/ | title=Management Transformed &#124; Research }}</ref> around co-location and distributed working which show that co-location is increasingly less relevant.

No matter which development method is followed, every team should include a [[customer representative]] (known as ''product owner'' in [[Scrum (software development)|Scrum]]). This representative is agreed by stakeholders to act on their behalf and makes a personal commitment to being available for developers to answer questions throughout the iteration. At the end of each iteration, the [[project stakeholder]]s together with the customer representative review progress and re-evaluate priorities with a view to optimizing the [[Rate of return|return on investment]] (ROI) and ensuring alignment with customer needs and company goals. The importance of stakeholder satisfaction, detailed by frequent interaction and review at the end of each phase, is why the approach is often denoted as a [[Customer centricity|customer-centered methodology]].<ref>{{Cite book |last1=Jain |first1=Parita |last2=Sharma |first2=Arun 
|last3=Ahuja |first3=Laxmi |title=2018 7th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO) |chapter=The Impact of Agile Software Development Process on the Quality of Software Product |date=August 2018 |chapter-url=https://ieeexplore.ieee.org/document/8748529 |location=Noida, India |publisher=IEEE |pages=812–815 |doi=10.1109/ICRITO.2018.8748529 |isbn=978-1-5386-4692-2 |s2cid=195775457}}</ref>

==== Information radiator ====
In agile software development, an '''information radiator''' is a (normally large) physical display, board with [[sticky note]]s or similar, located prominently near the development team, where passers-by can see it.{{sfn|Project Management Institute|2021|loc=§2.7.3.2 Information Radiators}} It presents an up-to-date summary of the product development status.<ref name=Ambler>{{cite book |title=Agile Modeling: Effective Practices for EXtreme Programming and the Unified Process |first=Scott |last=Ambler |date=12 April 2002 |isbn=978-0-471-20282-0 |publisher=John Wiley & Sons |pages=12, 164, 363}}</ref> A [[build light indicator]] may also be used to inform a team about the current status of their product development.