Software Development techniques cannot be enforced so how can an organization benefit from a decision to go Agile?

Will simply advertising a company as an Agile company do?

What are the internal policies, structural changes that an organization needs to fully realize the benefits of Agile?

My session will cover the various organizational policy implementations required to fully realize the benefits of Agile through policy guidelines.

To demonstrate this will be a case study of an implemented project that had a development lifecycle without the necessary process checkpoints in the organizational polcies due to which attrition, lack of quality controls and subjective, "Faith-based bias in selecting and using methods... and ignoring "Generally-accepted practice ..." resulted in a "maintenance-nightmare" software.

Policies are not implemented unless a good audit plan is in place and without good policies, adopting practices is usually only at a superficial level that is likely to crumble at the slightest challenge that may hinder a project's success.


Outline/Structure of the Case Study

A process model and Agile
A process audit plan
Is the plan right for Agile?
Incorporating the practices in the plan
How "not to" enforce practices
The case study
Q & A

Learning Outcome

Process Metrics, Process Analysis and organizational policies that affect an Agile project team's performance.
How documentation is important and in what context.

How policies should be implemented be it for CMM with Agile or ISO with Agile.

How teams should be trained to understand the context, attitude and practices while organizational changes happen or even, why organizational policy changes are necessary frequently even if it means inconveniencing their functions.


Target Audience

Developer, Tester, Database Designer, Traditional Project Manager, Product Owner, ScrumMaster, Agile coach, Business Analyst, Customer, HR and Quality professionals

schedule Submitted 6 years ago

Public Feedback