Disciplined Agile Software Development includes an iterative and evolutionary approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework with “just enough” ceremony that produces high quality solutions in a cost effective and timely manner which meets the changing needs of its stakeholders.
These methods have evoked substantial amount of literature and debates. However, academic research is still scarce, as most of existing publications are written by practitioners or consultants.
With this article, Java Code Geeks are trying to put together their available resources concerning Agile Software Development. So here is the list of all Agile Development articles for your reference:
- Save money from Agile Development
- Agile software development recommendations for users and new adopters
- Breaking Down an Agile process Backlog
- The Ten Minute Build
- Standups – take them or leave them
- How extreme is extreme programming?
- Even Backlogs Need Grooming
- You can’t be Agile in Maintenance? (Part 1)
- You can’t be Agile in Maintenance? (Part 2)
- Understanding the Vertical Slice
- Iterationless Development – the latest New New Thing
- How to start a Coding Dojo
- The Architecture Spike Kata
- 4 Warning Signs that Agile Is Declining
- Agile Before there was Agile: Egoless Programming and Step-by-Step
- Playing around with pomodoros
- Agile’s Customer Problem
- That’s Not Agile!
- Agile Lifecycles for Geographically Distributed Teams
- Software Engineering needs leaders, not ScrumMasters!
- Infrastructure, Technical Debt, and Automated Test Framework
- You don’t need Testers – Or do you?
- Why Does Management Care About Velocity?
- Programs and Technical Debt
- The pursuit of protection: How much testing is “enough”?
- Why an Agile Project Manager is Not a Scrum Master
- Are Agile plans Better because they are Feature-Based?
- Becoming a Leading Manager
- Product-Burndown-Charts and Sprint-Burndown-Charts in SCRUM Projects
- Where do Security Requirements come from?
- Measuring your IT OPS – Part 1
- Measuring your IT OPS – Part 2
- Agile Estimating: Story Points and Decay
- Sooner or Later: Deliver Early or Minimize Waste
- An agile methodology for orthodox environments
- Architects Need a Pragmatic Software Development Process
- In Agile development planning, a security framework loses out
- Hours, Velocity, Silo’d Teams, & Gantts
- Looking For Leaders In All The Wrong Places
- What Scrum, Kanban, RUP, and ITIL All Have In Common (which causes them to fail)
- Throughput Planning – Why Project Managers Should Like Lean and Agile
- Five Step Illustrated Guide to Setup a Kanban System in an Enterprise Organization
- The Demise of IT Business Analysts
- Build documentation to last – choose the agile way
- Client Reviews: From Waterfall to Agile
- What can you get out of Kanban?
- Does the PMI-ACP set the bar high enough on Risk Management?
- A Prototype is Worth a Thousand Lines of Code
- Contracting in Agile – You try it
Enjoy! And don’t forget to share and spread the word!
A FREE guide for agile teams.
Are you running retrospectives regularly? Perhaps you run retrospectives once a week, or fortnightly. Do you feel like you could be getting more out of your retrospectives and fuelling continuous improvement in your teams? You may already find retrospectives valuable, but suspect there are ways of making them better.