Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Ch. 9- Ten Common Agile Adoption Pitfalls -Abhinav Agarwal (12609041) Ch. 10- Ten Myths About Agile -Swati Gupta (12609048)
3 December 2013 Agile For Dummies 1
This chapter will help explore the ten common pitfalls organizations make when adopting agile strategies.
3 December 2013
3 December 2013
There is no compulsory rule to blindly follow the robust design of one agile strategy. Organization may change the same according to their unique needs.
3 December 2013
Improper Planning
There should be appropriate planning with regards to the agile strategies that are to be taken. Organization should ask itself Why, What, When & How as to the adoption of agile strategies.
3 December 2013
Agile should be a change in the culture of whole organization and not in just one of the processes.
3 December 2013
3 December 2013
3 December 2013
Insufficient Coaching
Many people dont like change and they are only comfortable working in their own space.
3 December 2013
When an organization adopts agile, it should try and not retain the traditional governance. Traditional governance is hard to change but it may have serious impact on agility.
3 December 2013
10
Skimping on Training
Agile involves a change in behavior and process.
So organization should send all of its team members to learn about agile and not just a few leads.
3 December 2013
11
Skimping on Tooling
Ensuring all team members consistently use tools impacts the success of the project.
Inconsistent use of tools may result into overall flow and quality issues.
3 December 2013
12
This chapter will help us understand what are common myths about agile and how they can be flipped off.
The agile approach to project management is far from a fad. Agile has been recently formalized with the Agile Manifesto and its associated principles.
Compared with traditional project management approaches, agile is better at producing successful projects.
3 December 2013
14
Sometimes agile can seem chaotic because its a very collaborative process. Agile requires rapid response time and flexibility from the team. Discipline is in fact greater than that in traditional systems.
Agile requires teams to reduce the feedback cycle on many activities, incrementally deliver a consumable solution, work closely with stakeholders throughout the life cycle, and adopt individual practices which require discipline in their own right.
3 December 2013
15
Agile rely on collaboration instead of big documentation. The planning is incremental and evolutionary, which has been proven successful.
3 December 2013
16
Agile teams keep documentation as lightweight as possible. They follow strategies, such as documenting continuously and writing executable specifications.
3 December 2013
17
Ideally agile teams are located within proximity of one another, but in this day and age, most development teams are distributed. If you use the proper tools, your team doesnt have to be collocated to work effectively together.
3 December 2013
18
Agile definitely scales. Large teams must be organized differently. Large agile teams succeed by using products like the following: IBM Rational Requirements Composer for requirements modeling . IBM Rational Build Forge for large-scale continuous integration IBM Rational Quality Manager to support parallel independent testing
3 December 2013
19
Regulated environments are those that are subject to some regulatory mandates, such as medical device companies, business in the finance area, governmental departments and offices, the healthcare field, and more. With agile, these organizations can feel confident when they endure time to time audits for regulatory compliance. They benefit from faster delivery of data and higher quality of their output.
3 December 2013
20
Agile is an iterative process, it provides the opportunity not just for greater control but better control over building the right things in the life cycle than one would have with the more traditional Waterfall approaches.
At the end of each iteration, the development team presents a completed product to the product owner for feedback.
Disciplined Agile Delivery (DAD) teams explicitly explore high-level requirements at the beginning of the project and seek to gain stakeholder agreement around the requirements.
3 December 2013 Agile For Dummies 21
Agile has explicit means of frequent feedback and loops, which means that developers and managers may feel more exposed to scrutiny. But that doesnt mean that agile wont work at your company.
Agile is a team approach. Roles are cross-functional and shared. Developers become testers and more frequent delivery creates more exposure and personal accountability.
3 December 2013
22
3 December 2013
23
Agile isnt needed for every team in every situation. Agile is a superb solution for projects that are in development or undergoing radical changes. For other projects, such as those that are in maintenance mode, agile isnt as good a fit. Projects that are under new product or rapid development, agile really is the best way to go.
3 December 2013
24
Thank You !
3 December 2013
25