close menu
Bookswagon-24x7 online bookstore
close menu
My Account
Home > Computing and Information Technology > Computer programming / software engineering > Running an Agile Software Development Project
Running an Agile Software Development Project

Running an Agile Software Development Project

          
5
4
3
2
1

Out of Stock


Premium quality
Premium quality
Bookswagon upholds the quality by delivering untarnished books. Quality, services and satisfaction are everything for us!
Easy Return
Easy return
Not satisfied with this product! Keep it in original condition and packaging to avail easy return policy.
Certified product
Certified product
First impression is the last impression! Address the book’s certification page, ISBN, publisher’s name, copyright page and print quality.
Secure Checkout
Secure checkout
Security at its finest! Login, browse, purchase and pay, every step is safe and secured.
Money back guarantee
Money-back guarantee:
It’s all about customers! For any kind of bad experience with the product, get your actual amount back after returning the product.
On time delivery
On-time delivery
At your doorstep on time! Get this book delivered without any delay.
Notify me when this book is in stock
Add to Wishlist

About the Book

A Practical Approach To Building Small To Medium Software Systems For Real Business Clients Based on more than 100 actual commercial projects, this book clearly explains how to run an agile software development project that delivers high-quality, high-value solutions to business clients. It concentrates on the practical, social, business, and management aspects as well as the technical issues involved. Professor Holcombe successfully connects readers with the wave of "Agile 2.0" concepts that take the techniques of agile development and place them in the service of business goals. Since it is widely believed that the use of Windows XP will become much more common in coming years, readers should be armed with cutting-edge knowledge of the latest practices in the field. Further features of the book include: Case studies provide real-world examples and describe how XP was introduced into the environment Analysis is provided to help readers determine which elements of XP are suitable for the unique challenges and environments for different projects Problems of a failing agile project and how they can be fixed are covered, including insight into which managerial techniques can be employed An Instructor's Guide provides practical advice on how to motivate students, organize real group projects, and deal, in a simple and effective way, with many of the problems that arise A sample syllabus, sample tests, and additional case study information are available on an instructor's password-protected ftp site Running an Agile Software Development Project is an indispensable guide for professional software developers, engineers, and project managers interested in learning how to use agile processes. It is also a valuable textbook for advanced undergraduate- and graduate-level students in computer engineering and software engineering courses.

Table of Contents:
Preface. Chapter 1: What is an agile methodology? 1.1 Rapid business change - the ultimate driver. 1.2 What must agile methodologies be able to do? 1.3 Agility - what is it and how do we achieve it? 1.4 Evolving software - obstacles and possibilities. 1.5 The quality agenda. 1.6 Do we really need all this mountain of documentation? 1.7 The human factor. 1.8 Some Agile Methodologies. 1.8.1 Dynamic Systems Development Method (DSDM). 1.8.2 Feature Driven Design (FDD). 1.8.3. Crystal. 1.8.4 Agile modeling. 1.8.5 SCRUM. 1.8.6 Summary table. 1.9 Review. Chapter 2: Extreme Programming Outlined. 2.1 Some guiding principles. 2.2 The five values. 2.3 The twelve basic practices of XP. 2.3.1 Test first programming. 2.3.2 Pair programming. 2.3.3 On-site customer. 2.3.4 The planning game. 2.3.5 System metaphor. 2.3.6 Small, frequent releases. 2.3.7 Always use the SIMPLEST solution that adds business value. 2.3.8 Continuous integration. 2.3.9 Coding standards. 2.3.10 Collective code ownership. 2.3.11 Refactoring. 2.3.12 Forty hour week. 2.4 Review. 2.5 The evidence for XP. 2.5.1 Evidence for Test First. 2.5.2 Evidence for pair programming. 2.5.3 Evidence for XP. 2.6 Preparing to XP. Chapter 3: Foundations - people and teams working together. 3.1 Software engineering in teams. 3.2 Personalities and team success. 3.3 Observations of team behaviour in XP projects. 3.4 Setting up a team. 3.5 Developing team skills. 3.6 Training together. 3.7 Finding and keeping a client for a university based project or a small business start up. 3.8 The organisational framework. 3.9 Planning. 3.9.1 PERT (Programme Evaluation and Review Technique). 3.9.2 Gantt Charts. 3.10 Dealing with problems. 3.10.1 Basic strategies. 3.10.2 When things go really wrong. 3.11 Risk analysis. 3.12 Review. Chapter 4: Starting an XP project. 4.1 Project beginnings. 4.1.1 Researching the business background. 4.1.2 Exploring the outline system description. 4.2 The first meetings with the client. 4.3 Business analysis and problem discovery. 4.4 The initial stages of building a requirements document. 4.5 Techniques for requirements elicitation. 4.6 Putting your knowledge together. 4.7 Getting technical. 4.8 Developing the requirements documents. 4.9 Specifying and measuring the quality attributes of the system. 4.10 The formal requirements document and system metaphor. 4.11 Contract negotiation. 4.12 Case study - the impact of organisational politics - learning from a failed project. 4.13 Review. Chapter 5: Identifying stories and preparing to build. 5.1 Looking at the user stories. 5.2 Collections of stories. 5.2.1 Pharmacovigilence. 5.2.2 Stamps system. 5.2.3 DELTAH (Developing European Leadership Through Action-learning in Healthcare). 5.3 User interfaces. 5.4 Communicating clearly with the customer and building confidence. 5.5 Demonstrating the non-functional requirements. 5.6 Estimating resources. 5.7 Review. Chapter 6: Bringing the system together as a coherent concept. 6.1 What is the problem? 6.2 A simple common metaphor. 6.3 Architectures and patterns. 6.4 Finite state machines. 6.5 Extreme modelling (XM). 6.6 Multiple stories and XXMs. 6.7 Building the architecture to suit the application - a dynamic system metaphor. 6.8 Another look at estimation. 6.9 Review. Chapter 7: Designing the system tests. 7.1 Preparing to build functional test sets. 7.1.1 Tests and testing. 7.1.2 Testing from a model. 7.1.3 Developing the model. 7.2 Testing with the Data in mind. 7.3 The full functional system testing strategy. 7.4 The thinking behind the system test process. 7.5 Design for test. 7.6 Test documentation. 7.7 Non-functional testing. 7.8 Testing internet applications and web sites. 7.9 Review. Chapter 8: Units and their tests. 8.1 Basic considerations. 8.2 Identifying the units. 8.3 Unit testing. 8.4 More complex units. 8.5 Automating unit tests. 8.5.1 Writing Unit Tests in JUnit. 8.6 Documenting unit test results. 8.7 Review. Chapter 9: Evolving the system. 9.1 Requirements change. 9.2 Changes to basic business model and functionality. 9.3 Dealing with change - refining stories. 9.3.1 Changes to the underlying data model. 9.3.2 Changes to the structure of the interface, perhaps the introduction of a new. 9.3.3 Adding a new function. 9.3.4 Changing the functionality of a function. 9.4 Changing the model. 9.4.1 Changing a process. 9.4.2 Removing states. 9.4.3 Adding states. 9.4.4. Adding a complete machine. 9.4.5 Adding processes. 9.5 Testing for changed requirements. 9.6 Refactoring the code. 9.7 Estimating the cost of change. 9.8 Summary. Chapter 10: Documenting and delivering the system. 10.1 What is documentation for and who is going to use it? 10.2 Coding standards and documents for programmers. 10.3 Coding standards for Java. 10.4 Maintenance documentation. 10.5 User manuals. 10.6 Version control. 10.6.1 The project archive. 10.6.2 Naming conventions. 10.7 Delivery and finalisation. 10.8 Summary. Chapter 11: Reflecting on the process . 11.1 Skills and lessons learnt. 11.2 The XP experience. 11.3 Personal and Team Assessment. 11.4 Summary. 11.5 Conundrums - discussion. Chapter 12: Lifestyle matters. 12.1 Keeping fit. 12.1.1 Correct sitting position. 12.1.2 Combating RSI. 12.2 General well-being. 12.3 Mental preparation. 12.4 Diet. 12.4.1 Diet and Brain function. 12.4.2 Summary of dietary information. 12.5 Music and work. 12.6 Conclusions and summary. References. Web sites. Index.


Best Sellers



Product Details
  • ISBN-13: 9780470385883
  • Publisher: John Wiley and Sons Ltd
  • Publisher Imprint: Wiley-Blackwell
  • Language: English
  • ISBN-10: 047038588X
  • Publisher Date: 25 Feb 2008
  • Binding: Other digital
  • No of Pages: 336


Similar Products

How would you rate your experience shopping for books on Bookswagon?

Add Photo
Add Photo

Customer Reviews

REVIEWS           
Click Here To Be The First to Review this Product
Running an Agile Software Development Project
John Wiley and Sons Ltd -
Running an Agile Software Development Project
Writing guidlines
We want to publish your review, so please:
  • keep your review on the product. Review's that defame author's character will be rejected.
  • Keep your review focused on the product.
  • Avoid writing about customer service. contact us instead if you have issue requiring immediate attention.
  • Refrain from mentioning competitors or the specific price you paid for the product.
  • Do not include any personally identifiable information, such as full names.

Running an Agile Software Development Project

Required fields are marked with *

Review Title*
Review
    Add Photo Add up to 6 photos
    Would you recommend this product to a friend?
    Tag this Book
    Read more
    Does your review contain spoilers?
    What type of reader best describes you?
    I agree to the terms & conditions
    You may receive emails regarding this submission. Any emails will include the ability to opt-out of future communications.

    CUSTOMER RATINGS AND REVIEWS AND QUESTIONS AND ANSWERS TERMS OF USE

    These Terms of Use govern your conduct associated with the Customer Ratings and Reviews and/or Questions and Answers service offered by Bookswagon (the "CRR Service").


    By submitting any content to Bookswagon, you guarantee that:
    • You are the sole author and owner of the intellectual property rights in the content;
    • All "moral rights" that you may have in such content have been voluntarily waived by you;
    • All content that you post is accurate;
    • You are at least 13 years old;
    • Use of the content you supply does not violate these Terms of Use and will not cause injury to any person or entity.
    You further agree that you may not submit any content:
    • That is known by you to be false, inaccurate or misleading;
    • That infringes any third party's copyright, patent, trademark, trade secret or other proprietary rights or rights of publicity or privacy;
    • That violates any law, statute, ordinance or regulation (including, but not limited to, those governing, consumer protection, unfair competition, anti-discrimination or false advertising);
    • That is, or may reasonably be considered to be, defamatory, libelous, hateful, racially or religiously biased or offensive, unlawfully threatening or unlawfully harassing to any individual, partnership or corporation;
    • For which you were compensated or granted any consideration by any unapproved third party;
    • That includes any information that references other websites, addresses, email addresses, contact information or phone numbers;
    • That contains any computer viruses, worms or other potentially damaging computer programs or files.
    You agree to indemnify and hold Bookswagon (and its officers, directors, agents, subsidiaries, joint ventures, employees and third-party service providers, including but not limited to Bazaarvoice, Inc.), harmless from all claims, demands, and damages (actual and consequential) of every kind and nature, known and unknown including reasonable attorneys' fees, arising out of a breach of your representations and warranties set forth above, or your violation of any law or the rights of a third party.


    For any content that you submit, you grant Bookswagon a perpetual, irrevocable, royalty-free, transferable right and license to use, copy, modify, delete in its entirety, adapt, publish, translate, create derivative works from and/or sell, transfer, and/or distribute such content and/or incorporate such content into any form, medium or technology throughout the world without compensation to you. Additionally,  Bookswagon may transfer or share any personal information that you submit with its third-party service providers, including but not limited to Bazaarvoice, Inc. in accordance with  Privacy Policy


    All content that you submit may be used at Bookswagon's sole discretion. Bookswagon reserves the right to change, condense, withhold publication, remove or delete any content on Bookswagon's website that Bookswagon deems, in its sole discretion, to violate the content guidelines or any other provision of these Terms of Use.  Bookswagon does not guarantee that you will have any recourse through Bookswagon to edit or delete any content you have submitted. Ratings and written comments are generally posted within two to four business days. However, Bookswagon reserves the right to remove or to refuse to post any submission to the extent authorized by law. You acknowledge that you, not Bookswagon, are responsible for the contents of your submission. None of the content that you submit shall be subject to any obligation of confidence on the part of Bookswagon, its agents, subsidiaries, affiliates, partners or third party service providers (including but not limited to Bazaarvoice, Inc.)and their respective directors, officers and employees.

    Accept

    New Arrivals



    Inspired by your browsing history


    Your review has been submitted!

    You've already reviewed this product!
    ASK VIDYA