Business Natural Languages Development in Ruby
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Tracking change and innovation in the enterprise software development community
Posted by Henrik Kniberg on Jun 27, 2007 01:18 PM
The tricky part to agile software development is that there is no manual telling you exactly how to do it. You have to experiment and continuously adapt the process until it suits your specific situation.
This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time.
Under the leadership of Henrik Kniberg they experimented with different team sizes, different sprint lengths, different ways of defining "done", different formats for product backlogs and sprint backlogs, different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. They also experimented with XP practices - different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum.
Your team's constraints may dictate a different configuration of practices (and even compromises), but here is an example of how to approach the "continuous improvement" process that will make your Agile process work best for you.
This book includes:
168 pages, 6" x 9", ISBN: 978-1-4303-2264-1
Courtesy of Henrik Kniberg and InfoQ.com, we're happy to offer a free version for download, to get this knowledge in as many peoples hands as possible. Login to download this book FREE (PDF)
If you enjoyed reading the free (non-printable) download version, please support the author and InfoQ's book series by buying the print version for only $22.95.
Foreward by Jeff Sutherland
Foreward by Mike Cohn
1. Introduction
2. How we do product backlogs
3. How we prepare for Sprint planning
4. How we do Sprint planning
5. How we communicate Sprints
6. How we do Sprint backlogs
7. How we arrange the team room
8. How we do daily Scrum
9. How we do Spring demos
10.How we do Spring retrospectives
11.Slack time between Sprints
12.How we do release planning and fixed priced contracts
13.How we combine Scrum with XP
14.How we do testing
15.How we handle multiple Scrum teams
16.How we handle geographically distributed teams
17.Scrum master checklist
18.Parting words
Recommended reading
About the Author
Henrik Kniberg is a consultant at Crisp in Stockholm (http://www.crisp.se), specializing in Java and Agile software development. He has founded several Swedish software companies and is passionate about learning, teaching, and applying the art of software development. Henrik takes a holistic approach and enjoys adopting different roles such as manager, developer, scrum master, teacher, and coach. For more info see http://www.crisp.se/henrik.kniberg.
IBM Agile Development eKit: Free Articles, Expert Q&A, Educational Resources
Rational Model Driven Development eKit: Examples, Tutorials, Webcasts
IBM Web 2.0 Developer eKit: Free Tutorials, Webcasts, Whitepapers
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.
Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.
David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.
Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.
In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.
William Soo and Meeraj Kunnumpurath discuss the Voca transaction processing system, architectural challenges and requirements, Voca's Spring/J2EE architecture, and the future SEPA architecture.
Security is about trade-offs. Only a few have the expertise to design good security. This talk focuses on Security Patterns, such as Role-based Access Control, Single Access Point, and Front Door.