You might have noticed that we use light-hearted blogs to introduce our white papers, which is fun but, admittedly, some people just want the facts. To make amends, we locked our funny man in a closet and asked a Really Serious Person to report on the white papers we’ve written about Agile and Lean development.
Take it away, Really Serious Person…
Agile Software Development: A Smart Choice for Outsourced Projects
Who should read it: If you need to hire a software development firm for an upcoming project and you’re wondering how Agile development compares with traditional waterfall methods, this white paper is for you.
What’s in it: We explain why more and more companies are replacing traditional waterfall development with Agile methods. We describe the basics of waterfall development, along with its major. Finally, we talk about Agile itself: key benefits, how it works, and some industry success stories.
Key takeaways: You’ll understand why Agile is a better approach than traditional waterfall methods. In particular, you’ll appreciate the business benefits of choosing an Agile firm.
In a nutshell: Agile 101.
Your Software Project…Approved: Discover Agile’s CapEx/OpEx Advantage
Who should read it: Budget-constrained managers who want to get their software projects done now should read this paper—twice!
What’s in it: We review accounting guidelines for how expenses are treated in software projects and we look at why some organizations find it advantageous to capitalize more of their development costs. We go on to examine how an Agile development process can give your organization the flexibility to capitalize more development costs than a traditional waterfall model allows. We then conclude the paper with a few questions that you might want to ask your CFO before proposing a new project.
Key takeaways: You’ll learn which software development costs can be CapEx and which ones are OpEx. You’ll understand how Agile can help bring the cost of your software project down to within your annual budget.
In a nutshell: Agile has accounting advantages that you should know about.
Sprint Zero: Where Your Software Project Begins
Who should read it: Read this white paper if you want to learn about how we plan a large software development project.
What’s in it: We tell you about Sprint Zero, an initial “research” effort that we can undertake to establish the feasibility of your software application. We describe key Sprint Zero activities like writing user stories, working out Definitions of Done, estimating development effort, building a Product Backlog, setting up essential architecture, creating a target release plan, and delivering training. We wind up the discussion with a brief look at the business benefits of kicking off your software project with a thorough planning effort.
Key takeaways: You’ll see how an Agile team translates your business requirements into actionable software specifications. You’ll appreciate the value of commissioning a standalone feasibility study before committing to a full-scale development effort.
In a nutshell: Good planning pays off.
Our Agile Development Process: A Customer’s Guide to Scrum
Who should read it: If you’re the designated Product Owner of the software application that we’ll be developing for your organization, this white paper is a must-read.
What’s in it: We explain Scrum from the point of view of a Product Owner. We describe the Product Owner’s principal responsibilities: writing and prioritizing user stories, developing acceptance criteria, and clarifying user stories for the Delivery Team during sprints.
Key takeaways: You’ll know what’s expected of a Product Owner in our Agile software development process.
In a nutshell: You’re in control of development.
Lean Software Development: Cutting Fat Out of Your Diet
Who should read it: Read this white paper if you want to know how lean thinking is being applied to software development.
What’s in it: We describe the seven principles of lean software development: eliminate waste, learn your way to the best solution, delay commitment, deliver quickly, have respect for people, build quality in, and optimize the top level. The paper concludes with a brief discussion of lean architecture and a look at some lean success stories.
Key takeaways: You’ll learn why lean developers can deliver high quality software more efficiently.
In a nutshell: How lean principles improve software development.
If you have questions about our Agile/Lean approach to software development, please contact us. We’d love to tell you more about what we do.
Stay tuned for the 2010 Architech “Book” Report, Part 2: White Papers about Proper Software Engineering…
