Agile software development ecosystems
Agile software development ecosystems
Agile Software Development with Scrum
Agile Software Development with Scrum
Assessing test-driven development at IBM
Proceedings of the 25th International Conference on Software Engineering
Lean Software Development: An Agile Toolkit
Lean Software Development: An Agile Toolkit
Practices Of An Agile Developer
Practices Of An Agile Developer
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Introducing Agile Development (XP) into a Corporate Webmaster Environment - An Experience Report
ADC '05 Proceedings of the Agile Development Conference
Analysis of the interaction between practices for introducing XP effectively
Proceedings of the 28th international conference on Software engineering
Agility and Discipline Made Easy: Practices from OpenUP and RUP (Addison-Wesley Object Technology (Paperback))
Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series)
Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series)
On the Sustained Use of a Test-Driven Development Practice at IBM
AGILE '07 Proceedings of the AGILE 2007
Outside-in software development: a practical approach to building successful stakeholder-based products
Hi-index | 0.00 |
Agile software development methods have proven to be a substantial catalyst for improvements in software quality, speed of delivery, and fitness for use, and are a driver behind the IBM Smarter Planet™ initiative, which involves intelligent approaches that address the needs of a world that is becoming increasingly interconnected and instrumented. Software vendors who use a traditional or waterfall approach (i.e., sequential software development process) for requirement analysis and development often find that they cannot react with sufficient speed to meet rapidly changing market demand. As a result, stakeholders must wait for the vendor to complete a lengthy development cycle, which, when complete, may miss the market window for the software or fail to adequately address other needs of these stakeholders. Agile development methods, as practiced across geographically diverse and broad development teams at IBM, directly address this issue. One purpose of this paper is simply to provide a brief high-level overview and record of the adoption of these practices and methods across a large company, i.e., the IBM Corporation.