Code Enigma
Web services plus sweets
Post-agile project development
Implication that we've moved beyond AgileCould have titled this Applying Agile in the real World
We base our ISO 9001 certification on Agile-scrum
Implication that we've moved beyond AgileCould have titled this Applying Agile in the real World
What is Agile (scrum)
A philosophy
Work done by self-managing, co-located teams in rapid iterations
What is it in practice
Building an extension
We have some issues
Costs
Specifications
Role of design
Delivery plans
Ownership
Why is it popular?
For customers
promises speedcut out "peripheral" costs for discovery, design, and testingallows for change - flexibleclient in charge
For suppliers
Feels like a good fit with Open Source fluid, transparent, organic collaborationNo paperwork is developer heavenProvide time rather than deliverablesit's a methodology
The problems in practice
Lack of product ownership
Owner doesn't want toOwner isn't allowed toOwner doesn't know how to
Can't write storiesCan't say no or stopThinks an estimate is a guaranteeBad judge of business value
Prioritising
Lack of prioritisationMeansA fixed specification
No scope for iterating
The requirements are visible and finite
The budget is fixed
Cost of 10 day sprints
1 x designer @ 500 = 5,0002 x developer @ 5000 = 10,0001 x scrum master @ 2,000
Total per sprint : 17,000
3 sprints : 51,000
Sizing the work
Working out business value expressed in user stories sized in t-shirts
User story
As anon I can view videos from the previous year's event so that I can judge the calibre of presenters
Developer response
No BDUF?
Cross-disciplinary, co-located, self-managing teams
Our responses
Decide if the project is Agile
Business planOrSpecification
Provide a clear, simple statement of the business aimProvide business objectives of how the application benefits users and consequently the clientProvide an MVPProvide an agreed model for how we work and communicateExplain the testing model and the definition of doneIdentify the people in each roleProvide a basis for review of progress
Product owner coaching and mentoring
Communication plan
document all communications avoid emailshared documentation
Project leader
The Real Owner
Project mentor
Client relationship manager
Time and task based estimating
Detailed time-tracking
Analyze the time
Prototype designs
Change requests
Are we still Agile ?
The Agile manifesto
We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value:
Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
That is, while there is value in the items onthe right, we value the items on the left more.
We're always balancing competing pressures
Top Related