Debunking Four Myths Of Agile Development

1y ago
24 Views
2 Downloads
4.70 MB
35 Pages
Last View : 1d ago
Last Download : 3m ago
Upload by : Oscar Steel
Transcription

Debunking Four Mythsof Agile DevelopmentDavid Rizzo, Director Product Development20151

Why is Agility Needed inthe Mainframe World Today?2

Why is Agility Needed inthe Mainframe World Today?3

Four Myths About Agile DevelopmentThere is only one wayto do Agile developmentAgile development meansfaster developmentOnly the IT organizationis impactedOrganizational procedures andstructures don’t have to change4

THERE IS ONLY ONE WAYTO DO AGILE DEVELOPMENT5

Agile: Methodology, Framework or ?When we wrote the agile manifesto, we knew it was not a methodology,and not a framework, either. It was and is a value center, a way oflooking at situations and thinking about how to proceed Scrum, on the other hand, is a framework Not a methodology, becauseit doesn’t even have enough in it to qualify as a methodology.-Alistair Cockburn (via blog post) Agile values:– Individuals and interactions over processes and tools– Working software over comprehensive documentation– Customer collaboration over contract negotiation– Responding to change over following a plan Don’t confuse “Agile” with its implementation6

Agile for Software Engineering7

Methodology Comparison8

Scrum TeamCross-functional RepresentationThe Scrum team is critical to Agile’s success. It must be comprised of the rightmembers from all disciplines that are needed to release the software product.9

Agile Change at CompuwareTraining Formal Change Managementtraining for key positions – Scrum Master– Scrum: enhancements – Two day, self-pacedScrum teams– Size: 7 2Agile team– Led by Scrum MasterAgile frameworks– Kanban: maintenanceAgile certification– Product Owner Organization– Team members Dedicated Scrum room Master Scrum Master– Pseudo Agile coach10

AGILE DEVELOPMENTMEANS FASTER DEVELOPMENT11

MVP – Minimum Viable Product Set of minimum capabilities that a user would accept Demonstrates future benefit to retain early adopters Provides Agile team maximum amount of feedback12

Efficient Task Execution Realize value sooner Reduce context switching Decrease total elapsed timeSource: Multitasking Gets You There oblems13

Agile Testing Integrated into designand development Automated testing– At each build, sprint andmilestone– Unit, integrationand system testing Applications designed for testing– Component architecture(Lego architecture)– Testing each component14

Agile Feeds DevOpsDevOps is a culture of communication, collaboration, integration, automationand measurement of cooperation between software Development and Operations.15

Fail Fast, Succeed Faster Fail safe vs. safe to fail Small failures, recover quickly Learn from failures and never repeat them Align with 99.999 mainframe reliability– Requires CI (Continuous Integration)– Fail in development and test,not production!16

ONLY THE I.T. ORGANIZATIONIS IMPACTED17

Business Agility is the Goal!18

Business Needs Are Met With AgilitySource: The Agile Advantage, CMG Partners – Sixth Annual CMO Agenda19

It’s More Than Just Engineering20

ORGANIZATIONALPROCEDURES ANDSTRUCTURES DON’TNEED TO CHANGE21

Agile Requires Executive SponsorshipSeriously, Agile requires changes in culture, processes and tools.It cannot succeed without executive management support.22

Embrace Change Agility, flexibility and ability to embrace(constant) change Continuous stakeholder feedback Transparency and collaboration Break down into granular initiatives Automation of manual steps Common instead of customized Fail fast – learn and adaptChange is difficult, but essential! People embrace change differently.Implement change training, not just Agile development training.23

Culture Change at Compuware24

Myths DebunkedAgile is a softwaredevelopment methodology25

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodology26

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodologyAgile development meansfaster development27

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodologyAgile development meansfaster developmentAgile development is aboutefficiency rather than speed28

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodologyAgile development meansfaster developmentAgile development is aboutefficiency rather than speedOnly the IT organizationis impacted29

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodologyAgile development meansfaster developmentAgile development is aboutefficiency rather than speedOnly the IT organizationis impactedAgile success requires agilitythroughout the business30

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodologyAgile development meansfaster developmentAgile development is aboutefficiency rather than speedOnly the IT organizationis impactedAgile success requires agilitythroughout the businessOrganizational proceduresand structures don’thave to change31

Myths DebunkedAgile is a softwaredevelopment methodologyAgile is a philosophy, selectthe right methodologyAgile development meansfaster developmentAgile development is aboutefficiency rather than speedOnly the IT organizationis impactedAgile success requires agilitythroughout the businessOrganizational proceduresand structures don’thave to changeAgile requires a change inculture, tools and processes32

Final Thoughts: Keys to Success Agile Software Developmentis Engineering’s contributionto Business Agility Focus on creating alignmentwith the rest of the business Quality is the responsibility ofthe team: win or lose as a team Collaborate and be transparentthroughout the entire business,not just within IT33

QUESTIONS34

2015 Compuware Corporation. All rights reserved.35

Training Formal Change Management training for key positions Agile certification -Product Owner -Scrum Master Agile team -Led by Scrum Master -Two day, self-paced Agile frameworks -Kanban: maintenance -Scrum: enhancements Scrum teams -Size: 7 2 -Team members Dedicated Scrum room Master Scrum Master

Related Documents:

1. The need for an agile way of working 6 2. The need for an agile way of working 9 3. Agile Core Values - Agile Project Management Vs. 10 Agile Event Management 4. Agile principles 12 _Agile Principles of Agile Project Management 13 _Agile Principles of VOK DAMS Agile Event Management 14 5. Agile Methods 16 _Scrum in Short 16 _Kanban in Short 18

1.1 Purpose of the Agile Extension to the BABOK Guide1 1.2 What is Agile Business Analysis?2 1.3 Structure6 Chapter 2:The Agile Mindset 2.1 What is an Agile Mindset?7 2.2 The Agile Mindset, Methodologies, and Frameworks8 2.3 Applying the Agile Mindset9 2.4 Agile Extension and the Agile Ma

Agile Estimating and Planning by Mike Cohn Agile Game Development with Scrum by Clinton Keith Agile Product Ownership by Roman Pichler Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and .

Agile World View "Agility" has manydimensions other than IT It ranges from leadership to technological agility Today's focus is on organizational & enterprise agility Agile Leaders Agile Organization Change Agile Acquisition & Contracting Agile Strategic Planning Agile Capability Analysis Agile Program Management Agile Tech.

The most popular agile methodologies include: extreme programming (XP), Scrum, Crystal, Dynamic Sys-tems Development (DSDM), Lean Development, and Feature Driven Development (FDD). All Agile methods share a common vision and core values of the Agile Manifesto. Agile Methods: Some well-known agile software development methods include: Agile .

1. Agile methods are undisciplined and not measurable. 2. Agile methods have no project management. 3. Agile methods apply only to software development. 4. Agile methods have no documentation. 5. Agile methods have no requirements. 6. Agile methods only work with small colocated teams.-7. Agile methods do not include planning. 8.

The Agile Customer . 9/6/2012 6 Agile Development Team Agile Analyst . 9/6/2012 7 Agile Programmer Agile Tester . 9/6/2012 8 Agile Manager Agile Usability Designer . 9/6/2012 9 Kicking off a project The Inception Deck –Ten questions you’d be crazy not to ask before starting any

possibility of a leak from a storage tank? MANAGING RISK This starts with the design and build of the storage tank. International codes are available, for example API 650, which give guidance on the matter. The following is an extract from that standard: 1.1.1 This standard covers material, design, fabrication, erection, and testing