- Innovative Product Development
- Intelligent Systems
- Lifecycle Experience
- Information Systems
- Mechanical Engineering
- Altran Delivery Model (ADM)
Agile Software Development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
Principles behind the Agile Manifesto
1. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
2. Deliver working software frequently, from a couple of weeks to a couple of months, with a reference to the shorter timescale.
3. Business people and developers must work together daily throughout the project.
4. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
5. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
6. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
7. Working software is the primary measure of progress.
8. Continuous attention to technical excellence and good design enhances agility.
9. Simplicity--the art of maximizing the amount of work not done--is essential.
10. The best architectures, requirements, and designs emerge from self-organizing teams.
11. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Lean, Scrum, XP: How do they relate?
They all have one thing in common: Eliminate Waste
“Waste” being anything which does not advance the process, or add value. “Value” being any action or process that a customer would be willing to pay for.
Scrum is the most used agile implementation, it’s iterative, incremental. Its use has focused on the management of software development projects, and it can be used to run software maintenance teams, or as a general project/program management approach. Exist since 1995.
- XP Programming (XP)
Is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements? It advocates frequent "releases" in short development cycles (time boxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted. Exist since 1996.
- Test Driven Development (TDD)
Is a software development process that relies on the repetition of a very short development cycle: first the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refactors the new code to acceptable standards? Exist since 1996.
- Lean Software Development
Is a translation of Lean manufacturing and Lean IT principles and practices to the software development domain? Adapted from the Toyota Production System in 2003.
There are no silver bullets, but it dramatically increases your chances of success while bringing out the best your team has to offer.