Из-за периодической блокировки нашего сайта РКН сервисами, просим воспользоваться резервным адресом:
Загрузить через dTub.ru Загрузить через ClipSaver.ruУ нас вы можете посмотреть бесплатно Expediency & Fluency by Vinod Kumaar Ramakrishnan или скачать в максимальном доступном качестве, которое было загружено на ютуб. Для скачивания выберите вариант из формы ниже:
Роботам не доступно скачивание файлов. Если вы считаете что это ошибочное сообщение - попробуйте зайти на сайт через браузер google chrome или mozilla firefox. Если сообщение не исчезает - напишите о проблеме в обратную связь. Спасибо.
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса savevideohd.ru
A lot of companies have adopted scrum and gone into the mode of creating a predictable delivery mechanism where you can easily track and trace a requirement and ship it. What has been lost in the due course is handling frequent requirement changes, scrum has gone into a prescriptive model leaving the value and intent behind. If I have to summarise why a lot of projects fail, it is due to two things that never work in tandem. They are expediency and fluency. Expediency is the ability to find a quick way to address a solution which is simple, effective though not a complete one. Richard Gabriel talks about this in Worse is better https://en.wikipedia.org/wiki/Worse_i... , it is particularly very helpful in first mover advantage situations and product market fit cases. The simplicity of the solution will also make it easy to amend and extend based on the feedback. Communication and shared understanding across the entire group is the key to expediency and that is where a small team always excels at. Fluency is the capability to do the right things fast. It is the ability of the people to do things repeatedly without getting fatigued or bored by a healthy blend of capabilities of people, process and engineering. If the team has a robust continuous delivery pipeline, they would not worry about making frequent changes to production. If the team members are highly skilled and disciplined you need less management oversight to make them to follow the right things. If the culture is established that visibility of work is a right and people have a good degree of control/autonomy over how work is done then we have a lot of motivated individuals to realise the goals. If the org is expedient alone, it creates a lot of fatigued individuals. If it is fluent alone, it creates a lot of bored individuals. To be productive the creative tension between expediency and fluency has to be exploited. More details: https://confengine.com/conferences/ag... Conference Link: https://2025.agileindia.org