Bu sunum serisi, Agile yöntemlerin değişimi verimli yönetebilmek, çabuk ve kaliteli üretebilmek gibi bilinen getirileri dışında, alternatif getirilerini ortaya koymak amacıyla hazırlanmıştır.
Bu sunumda Agile yöntemlerin Turn-Over ve Motivasyona olan katkısı ele alınmıştır.
Bu sunum serisi, Agile yöntemlerin değişimi verimli yönetebilmek, çabuk ve kaliteli üretebilmek gibi bilinen getirileri dışında, alternatif getirilerini ortaya koymak amacıyla hazırlanmıştır.
Bu sunumda Agile yöntemlerin sürekli iyileştirmeye katkısı ele alınmıştır.
These presentation series are subjected to explore the alternative yields of Agile methods besides the well known ones; Managing Changing Priorities, better Time to Market, Higher Quality...
Alternatives to Go Agile / Turn Over - MotivationACM
Ìý
These presentations explore alternative benefits of Agile methods beyond well-known benefits like managing changing priorities, faster time to market, and higher quality. Agile frameworks like Scrum are considered. Turnover and motivation are discussed as Turkish IT professional statistics show most have less than 10 years experience and change jobs every 1-2 years, costing companies significantly. Reasons for job changes include lack of satisfaction, pay, growth and fun. Agile solutions that incorporate autonomy, mastery and purpose are proposed to improve motivation and performance through self-organization.
Bu sunum serisi, Agile yöntemlerin değişimi verimli yönetebilmek, çabuk ve kaliteli üretebilmek gibi bilinen getirileri dışında, alternatif getirilerini ortaya koymak amacıyla hazırlanmıştır.
Bu sunumda Agile yöntemlerin şeffaflığa katkısı ele alınmıştır.
The document discusses key elements of agile metrics for organizations. It recommends measuring outcomes like working software over individual activities. Good metrics focus on time to market, value, and innovation at both the organizational and team level. Examples of metrics include percentage of features completed, release frequency, customer satisfaction, and defect rates. Metrics should be transparent and encourage continuous learning.
Agile transformation is no more that much challenging with our unique way of leading agility. In order to enhance agility and adopt an Agile culture, it is crucial to lead the change activities in multiple levels; daily processes of teams, organizations structure and its operating model, demand handling. Together with well established governance teams and a sharply focused roadmap, benefits will rise sooner.
Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.
The document discusses the characteristics of an agile work environment and compares them to a potentially less agile status quo. An agile approach emphasizes face-to-face, open communication among self-organizing collaborative teams; decisions are made as a group while ensuring accountability. Work is done in short cycles with frequent delivery and improvement, customer involvement, and transparency into progress.
The document discusses challenges with traditional waterfall software development approaches and makes the case for adopting agile methodologies. Some key points:
- Traditional approaches focus too much on upfront planning and scope definition, which often leads to changes later on that cause delays and missed deadlines.
- Agile prioritizes delivering working software frequently in short iterations to get early customer feedback and make adjustments more easily.
- Scrum is introduced as a popular agile framework that emphasizes self-organizing cross-functional teams, short development cycles called sprints, and flexibility to change requirements.
- A transformation is needed across the organization to shift from traditional command-and-control styles to collaborative agile values like continuous
This presentation is prepared as part of nonprofit co-operation between ACM and Turkish universities to explore Agility together with graduate students.
This document discusses transforming an organization to an agile methodology. It recommends starting small with agile practices, scaling up successes as experience is gained, and focusing on changing people's mindsets, values, and culture to fully embrace agile principles.
The document discusses the key aspects of being agile from the perspective of ACM Software, an agile consultancy company. It emphasizes that being agile means frequently delivering and adapting to changes, creating high-performing cross-functional teams, and focusing on customer delight. It stresses that the secret to achieving agility is focusing on people by empowering them through self-organizing teams and transforming company culture through daily agile practices and values.
Bu döküman ACM tarafından hazırlanmış olup, hazırlanmasında Scrum'ın yaratıcıları Ken Schwaber ve Jeff Sutherland tarafından yayınlanan Scrum Guide referans alınmıştır.
This document discusses the need for companies to adapt to rapid changes in the world by embracing agile and lean principles. It notes that the world is changing quickly in many areas like technologies, tools, behaviors and organizations. It then highlights research showing that the majority of traditional projects fail or go over budget and time. This emphasizes the importance of being agile to respond to changing requirements and priorities. The document promotes agile methodologies like Scrum, Kanban, and principles of lean and software craftsmanship to help organizations and teams continuously deliver value to customers.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
This document provides advice for businesses to improve agility based on examples from successful companies. It recommends listening closely to customers to build strong relationships, frequently delivering new outputs each week like Zara, leading change and being innovative like FujiFilm, and emphasizing teamwork which is the foundation of agile management.
Agility Check-Up is an assessment that evaluates Agile teams and organizations across six perspectives: maturity of roles, teamwork, inspect and adapt processes, transparency, business alignment, and learning organization. Consultants assess each perspective through surveys, meetings, team room visits, and communication to determine maturity levels and identify improvement actions. The assessment aims to help teams and organizations adapt to change and improve their agility.
Agile transformation is no more that much challenging with our unique way of leading agility. In order to enhance agility and adopt an Agile culture, it is crucial to lead the change activities in multiple levels; daily processes of teams, organizations structure and its operating model, demand handling. Together with well established governance teams and a sharply focused roadmap, benefits will rise sooner.
Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.
The document discusses the characteristics of an agile work environment and compares them to a potentially less agile status quo. An agile approach emphasizes face-to-face, open communication among self-organizing collaborative teams; decisions are made as a group while ensuring accountability. Work is done in short cycles with frequent delivery and improvement, customer involvement, and transparency into progress.
The document discusses challenges with traditional waterfall software development approaches and makes the case for adopting agile methodologies. Some key points:
- Traditional approaches focus too much on upfront planning and scope definition, which often leads to changes later on that cause delays and missed deadlines.
- Agile prioritizes delivering working software frequently in short iterations to get early customer feedback and make adjustments more easily.
- Scrum is introduced as a popular agile framework that emphasizes self-organizing cross-functional teams, short development cycles called sprints, and flexibility to change requirements.
- A transformation is needed across the organization to shift from traditional command-and-control styles to collaborative agile values like continuous
This presentation is prepared as part of nonprofit co-operation between ACM and Turkish universities to explore Agility together with graduate students.
This document discusses transforming an organization to an agile methodology. It recommends starting small with agile practices, scaling up successes as experience is gained, and focusing on changing people's mindsets, values, and culture to fully embrace agile principles.
The document discusses the key aspects of being agile from the perspective of ACM Software, an agile consultancy company. It emphasizes that being agile means frequently delivering and adapting to changes, creating high-performing cross-functional teams, and focusing on customer delight. It stresses that the secret to achieving agility is focusing on people by empowering them through self-organizing teams and transforming company culture through daily agile practices and values.
Bu döküman ACM tarafından hazırlanmış olup, hazırlanmasında Scrum'ın yaratıcıları Ken Schwaber ve Jeff Sutherland tarafından yayınlanan Scrum Guide referans alınmıştır.
This document discusses the need for companies to adapt to rapid changes in the world by embracing agile and lean principles. It notes that the world is changing quickly in many areas like technologies, tools, behaviors and organizations. It then highlights research showing that the majority of traditional projects fail or go over budget and time. This emphasizes the importance of being agile to respond to changing requirements and priorities. The document promotes agile methodologies like Scrum, Kanban, and principles of lean and software craftsmanship to help organizations and teams continuously deliver value to customers.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
This document provides advice for businesses to improve agility based on examples from successful companies. It recommends listening closely to customers to build strong relationships, frequently delivering new outputs each week like Zara, leading change and being innovative like FujiFilm, and emphasizing teamwork which is the foundation of agile management.
Agility Check-Up is an assessment that evaluates Agile teams and organizations across six perspectives: maturity of roles, teamwork, inspect and adapt processes, transparency, business alignment, and learning organization. Consultants assess each perspective through surveys, meetings, team room visits, and communication to determine maturity levels and identify improvement actions. The assessment aims to help teams and organizations adapt to change and improve their agility.
Agile için Alternatif Nedenler / Turn-Over ve Motivasyon
1. Bu sunum serisi, Agile yöntemlerin
Değişimi Yönetebilmek, Daha Çabuk ve
Kaliteli Ãœretebilmek gibi bilenen getirileri
dışında, alternatif getirilerini
ortaya koymak amacıyla hazırlanmıştır
Bu sunumda Scrum prensip ve pratikleri temel alınmıştır
Copyright 2007, ACM. All rights reserved
2. Agile için Alternatif Nedenler
Turn-Over ve Motivasyon
by Ahmet AkdaÄŸ
Copyright 2007, ACM. All rights reserved
3. Bilgisayar Mühendisleri Odası 2009
verilerine göre;
Çalışanlarının %71’i 0-9 yıl tecrübeli
kişilerden oluşan Türkiye bilişim sektöründe
personelin %60‘ı 3. iş yerinde
çalışıyor
http://www.bmo.org.tr/wp-content/uploads/2011/08/AnketSonucRaporuv2.pdf
Copyright 2007, ACM. All rights reserved
4. Bir işte ortalama çalışma süresi
12-30 ay
aralığında değişiyor
Copyright 2007, ACM. All rights reserved
5. Ortalamaya bakılırsa bir çalışan genelde en
çok verim üreteceği sırada işten ayrılmış
oluyor
Copyright 2007, ACM. All rights reserved
7. Yeni eleman arama ve iÅŸe yerleÅŸtirme maliyeti
Copyright 2007, ACM. All rights reserved
8. Yeni eleman arama ve iÅŸe yerleÅŸtirme maliyeti
Uygun kiÅŸiyi bulamama riski
Copyright 2007, ACM. All rights reserved
9. Yeni eleman arama ve iÅŸe yerleÅŸtirme maliyeti
Uygun kiÅŸiyi bulamama riski
Yeni gelen kişinin adaptasyon süresi ve o süreç
içerisinde yapabileceği hataların maliyeti
Copyright 2007, ACM. All rights reserved
10. Yeni eleman arama ve iÅŸe yerleÅŸtirme maliyeti
Uygun kiÅŸiyi bulamama riski
Yeni gelen kişinin adaptasyon süresi ve o süreç
içerisinde yapabileceği hataların maliyeti
Yeni çalışanın tam kapasiteye ulaşması için geçen
süredeki fırsat maliyeti
Copyright 2007, ACM. All rights reserved
11. Toplamda bu süreç şirkete ayrılan kişinin
maliyetinin 4-8 katı olarak geri
dönmektedir
Copyright 2007, ACM. All rights reserved
14. İş tatminsizliği(Genelde zaman yönetimi eksikliğinin
kalitesiz işler çıkarılmasına neden olması)
Copyright 2007, ACM. All rights reserved
15. İş tatminsizliği(Genelde zaman yönetimi eksikliğinin
kalitesiz işler çıkarılmasına neden olması)
Yazılım geliştirmenin meslek olarak algılanmaması
nedeniyle maaşların yükselememesi
Copyright 2007, ACM. All rights reserved
16. İş tatminsizliği(Genelde zaman yönetimi eksikliğinin
kalitesiz işler çıkarılmasına neden olması)
Yazılım geliştirmenin meslek olarak algılanmaması
nedeniyle maaşların yükselememesi
Kişisel gelişimin zayıflaması
Copyright 2007, ACM. All rights reserved
17. İş tatminsizliği(Genelde zaman yönetimi eksikliğinin
kalitesiz işler çıkarılmasına neden olması)
Yazılım geliştirmenin meslek olarak algılanmaması
nedeniyle maaşların yükselememesi
Kişisel gelişimin zayıflaması
İşin eğlenceye dönüşememesi, rutinliğin artması
Copyright 2007, ACM. All rights reserved
18. İş tatminsizliği(Genelde zaman yönetimi eksikliğinin
kalitesiz işler çıkarılmasına neden olması)
Yazılım geliştirmenin meslek olarak algılanmaması
nedeniyle maaşların yükselememesi
Kişisel gelişimin zayıflaması
İşin eğlenceye dönüşememesi, rutinliğin artması
Yönetimsel zaaflar
Copyright 2007, ACM. All rights reserved
19. İş tatminsizliği(Genelde zaman yönetimi eksikliğinin
kalitesiz işler çıkarılmasına neden olması)
Yazılım geliştirmenin meslek olarak algılanmaması
nedeniyle maaşların yükselememesi
Kişisel gelişimin zayıflaması
İşin eğlenceye dönüşememesi, rutinliğin artması
Yönetimsel zaaflar
...
Copyright 2007, ACM. All rights reserved
25. Autonomy-Mastery-Purpose
Kendini yöneten ve organize eden
takımlarda motivasyon, performans,
sorumluluk duygusu yükselmektedir
Copyright 2007, ACM. All rights reserved
28. Doğru uygulanan Agile süreçler ile hedef
odaklı enerjik takımlar oluşturularak
güncel ve kaliteli yazılımlar
üretilebilmektedir
80.000
üzerinde
IT
projesi
Standish Group
Copyright 2007, ACM. All rights reserved
29. www.acm-software.com
@ACMSoftware
@aakdag
Copyright 2007, ACM. All rights reserved