Why Every CTO Should Realize That Agile Manifesto Is No Longer Valid
Tags: agile, development, engineering, cto
Published: 2019-08-30 13:39:09

---
title: Why Every CTO Should Realize That Agile Manifesto Is No Longer Valid
published: true
description: 
tags: agile, development, engineering, CTO
---

![agile manifesto](https://miro.medium.com/max/1200/1*OS4OtkNSktdBtOPSW2fwfg.png)

So much is said about motivation among developers and how to effectively manage a Tech team. There are dozens of guides and top tips widely spread across the internet, but have you ever wondered what your developers think? What do they expect? And what would make their job more effective?

##It’s time for a 21st-century successor to Agile — Async Software Development.##

Here are the **4 points you need to bear in mind to keep your tech team satisfied:**

##1. Modern tools##

Take advantage of async collaboration tools like GitLab, GitHub, Bitbucket. All of them provide three basic features:

✔ Each deeply integrates version control with issue tracking.

✔ Each offers rich prioritization and assignment features.

✔ Each wraps all that up into a slick user experience that any member of the team can use, including nontechnical employees.

##2. Flexible work environments##

Let people decide for themselves. Some people work better in crowds, others work better at home. Some love open space, others need more privacy. Some are early birds, others — night owls. Don’t assign desks to anyone by default, instead, adopt a [hotelling policy](http://en.wikipedia.org/wiki/Hotelling_%28office%29) at your office.

##3. Meetings only as a last resort##

✔ Forget the planning meetings. Product owners may fill issues in the issue tracker, assign priority, assign them to people, and set a release milestone. Your engineers will know what to do by simply working on whatever the highest priority issue is in their queue.

✔ Skip the daily standups. Product owners may check the status in comment threads of issues and post a question when needed.

✔ Give up the backlog grooming sessions. Product owners review issue queue and should reassess priority on their own reaching out to others for advice when necessary.

[Creative professionals need long stretches of uninterrupted time](http://www.ted.com/talks/jason_fried_why_work_doesn_t_happen_at_work), so arrange a meeting only when all other channels of communication aren’t suitable for a specific issue.

##4. Comprehensive documentation##

With better-documented workflow, your workers won’t need to interrupt each other to search for ‘tribal knowledge’. Putting an answer in a FAQ or other form of async communication is much better than a constant [shoulder tap](https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-a-programmer/).

If you are a technology-driven organization you must be aware that everything changes, even approach to work. Try to understand your people better and they will repay you.


##I am really wondering what do you think of this new approach?##
So please, leave your comment.


Based on: [Manifesto for Async Software Development](http://asyncmanifesto.org/).

Also posted here: [https://javashop.pl/why-every-cto-should-realize-that-agile-manifesto-is-no-longer-valid/](https://javashop.pl/why-every-cto-should-realize-that-agile-manifesto-is-no-longer-valid/)