sabato 27 marzo 2010
The basics of being Agile in a real-time embedded systems environment: Part 1
The basics of being Agile in a real-time embedded systems environment: Part 1: "In a three part tutorial, Bruce Powel Douglass, author of "Real-Time Agility," presents a convincing argument as to why agile approaches are now necessary in embedded software development and how the techniques can be used in the context of real-time embedded applications. Part 1: What is agile development and why use it.
Iscriviti a:
Commenti sul post (Atom)
Much as I love my BlackBerry, I was amazed that a customer service representative recommended removing the battery to reboot the device daily.
RispondiElimina
RispondiEliminaThe Agile Manifesto
A good place to start to understand agile methods is with the agile manifesto. The manifesto is a public declaration of intent by the Agile Alliance, consisting of 17 signatories including Kent Beck, Martin Fowler, Ron Jeffries, Robert Martin, and others. Originally drafted in 2001, this manifesto is summed up in four key priorities:
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to change over following a plan
To support these statements, they give a set of 12 principles. I'll state them here to set the context of the following discussion:
1) Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2) Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3) Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4) Business people and developers must work together daily throughout the project.
5) Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6) The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7) Working software is the primary measure of progress.
8) Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9) Continuous attention to technical excellence and good design enhances agility.
10) Simplicity — the art of maximizing the amount of work not done — is essential.
11) The best architectures, requirements, and designs emerge from self-organizing teams.
12 At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Eccovi la seconda parte ...
RispondiEliminaEccovi la terza parte ...
RispondiElimina