Thursday, February 10, 2011
Show Me New Design Salwar
An organization that requires agility in the execution of your software projects requires the establishment of policies to ensure early and continuous delivery devices and services of value and utility software.
then describe a set of policies that I have used in consultancies, which enable the organization away from the model of traditional software development where there was a collection of information for 3 months, then 2 months for development. This type of development did not allow early delivery of value and did not consider the following facts:
- is impossible to meet all requirements at the beginning of a project.
- activity analysis and design is no guarantee that there will be changes.
- will always be deviations in time and resources.
General Guidelines
- The project should be implemented in incremental iterations with a product demonstration at the end of each iteration of this policy, will know the status of the project, assessing whether the conditions meet customer expectations, if the quality is expected, or if there is delays, speeding decision making corrective .
- The project will be implemented in incremental iterations with a fixed duration of 3 weeks.
- prioritized requirements will be developed by the value delivered to the client: This policy will allow the most important objectives of the project are addressed.
- control and monitoring of the project is completed based on the requirements in each iteration. Is understood as a requirement, deliverables related to: analysis, development, testing, documentation, etc. and integrated with the deliverables of the previous iterations.
- Each requirement must be independent of other requirements, as far as possible.
- Each requirement must be demonstrated, allowing the customer how to check that the requirement is completed and meet their expectations.
- The requirement should be a degree of effort to be completed similar to the other requirements, so that the organization and the customer can make an extrapolation of the progress of the project.
- The software component, should be developed and released in parts, and not delivered at the end of the project.
- The development of software component that will make up the solution should be released in several iterations.
- Each iteration should produce production-quality software, tested, integrated, and documented (functional art).
- Each iteration must comply with a subset of requirements.
- Each iteration should consider (analysis, design, implementation, documentation, etc.). Tests
- Each project must incorporate the practices of TDD (Test Driven Development).
- Each of the deliverables should contain unit test scripts, comprehensive, functional, etc., using frameworks such as JUnit, dbunit, mockObjtects, etc.
- Documentation Documentation of projects, specifically: user manual, operation manual, solution architecture, specifications, etc., should be partial deliverables for each of the iterations, ie, documentation not be released at the end of the project, but partial delivery.
- Each of the deliverables will be submitted a quality script that run the organization, and will not be accepted as products of the project to achieve an acceptable level.
- Risks will be identified in the first iteration, also taking out an initial assessment of exposure to risk and contingency plans. In each iteration will be reviewed and updated the document "Risk List", then add the list of major risks updated each iteration.
- Each project artifacts should be kept under a version control system.
- The organization make available a version control system, which must be updated by the client remotely.
"It's amazing the change that can occur in an organization the incorporation and implementation of agile software development."
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment