Agile Software Development: Best Practices for Large by Thomas Stober, Uwe Hansmann

By Thomas Stober, Uwe Hansmann

Software program improvement is relocating in the direction of a extra agile and extra versatile method. It seems that the normal "waterfall" version isn't really supportive in an atmosphere the place technical, monetary and strategic constraints are altering nearly each day. yet what's agility? What are today’s significant methods? and particularly: what's the impression of agile improvement rules at the improvement groups, on undertaking administration and on software program architects? How can huge firms turn into extra agile and enhance their enterprise procedures, which were current due to the fact that many, decades? What are the constraints of Agility? and what's the perfect stability among trustworthy constructions and suppleness? This ebook will provide solutions to those questions. a powerful emphasis may be on genuine existence undertaking examples, which describe how improvement groups have moved from a waterfall version in the direction of an Agile software program improvement strategy.

Show description

Read or Download Agile Software Development: Best Practices for Large Software Development Projects PDF

Best software development books

Managing Humans: Biting and Humorous Tales of a Software Engineering Manager

Handling people is a range of the simplest essays from Michael Lopp's site, Rands in Repose. Drawing on Lopp's administration reviews at Apple, Netscape, Symantec, and Borland, this booklet is filled with tales in response to businesses within the Silicon Valley the place humans were recognized to yell at one another.

Essential Software Architecture (2nd Edition)

Task titles like "Technical Architect" and "Chief Architect" these days abound within the software program undefined, but many folks suspect that "architecture" is among the such a lot overused and least understood phrases in specialist software program improvement. Gorton's booklet is helping unravel this trouble.

Official (ISC)2 Guide to the CSSLP ((ISC)2 Press)

Because the international chief in details protection schooling and certification, (ISC)2® has a confirmed song checklist of training and certifying info defense pros. Its most modern certification, the qualified safe software program Lifecycle specialist (CSSLP®) is a testomony to the organization’s ongoing dedication to info and software program protection.

Lehrbuch der Softwaretechnik: Basiskonzepte und Requirements Engineering

Die Softwaretechnik bildet einen Grundpfeiler der Informatik. Jede Softwareentwicklung basiert auf Prinzipien, Methoden und Werkzeugen. Mit Basiskonzepten kann die Statik, Dynamik und Logik von Softwaresystemen beschrieben und modelliert werden. Die Anforderungen an ein neues Softwareprodukt zu ermitteln, zu spezifizieren, zu analysieren, zu validieren und daraus eine fachliche Lösung abzuleiten bzw.

Extra resources for Agile Software Development: Best Practices for Large Software Development Projects

Example text

In the waterfall approach, the test teams are usually separate from the development teams. The test team receives the documentation (and a good specification can be a clear advantage) and verifies the product against that specification. There also needs to be good product documentation right at the start of the testing phase to allow the test teams to be productive. But it is almost impossible to carry out larger projects or projects with some level of innovation without change. It could be as simple as a client becoming more concrete with his ideas and requirements after they have seen a prototype or a first working version of the solution.

Prototypes or screen mockups are often useful to ensure that the stakeholders and the team have the same interpretation of the requirements. Often the stakeholders’ requirements evolve during the requirements discussion, as the discussion becomes more concrete. Especially during the waterfall approach it is important that the requirements are completely captured and agreed on before the team moves to the design phase, as every new or changing requirement means that the team needs to go back to the requirements phase, which may invalidate work that was already done in an earlier phase.

15). By doing so the whole project becomes more flexible to react to change and changing requirements. As the design for the complete solution is now done in steps and not overall at the beginning, there may be a higher risk that in a later round the designs and the code that were done before need to be changed again to support requirements that are just addressed in this round. This approach also addresses the issue of the waterfall approach – that it takes until the test phase to see the first integrated and working code.

Download PDF sample

Rated 4.62 of 5 – based on 23 votes