Tad Anderson

Subscribe to Tad Anderson: eMailAlertsEmail Alerts
Get Tad Anderson via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Tad Anderson

At the beginning of the book the authors say they created this book to be used in a classroom setting. I agree that it is a great book for the classroom, but I would also recommend it to anyone who wants to learn about the current Agile methodologies. It does what the title of the book says it does, and it introduces the reader to Agile methods. It starts with a nice introduction to the Agile movement's history and then covers all the traditional topics that fall within the Agile purview. I have listed the chapters below to give you a high level view of the topics covered. Chapter 1. The History and Value of Agile Software Development Chapter 2. Organizational Culture Considerations with Agile Chapter 3. Understanding the Different Types of Agile Chapter 4. Describing the Different Roles Chapter 5. The New Way to Collect and Document Requirements Chapter 6. Grooming and Pl... (more)

Developing Quality Technical Information: Third Edition

As an enterprise and software architect the one thing I hate most about my job is documentation, yet the importance of doing documentation on sizable projects is what I find myself preaching about the most. One reason I understand the importance of documentation is that I came from an electronic engineering background. As an electronic engineer 93% - 97% of my time was consumed doing proof of concepts and documentation. Almost all of that time was documentation. It was just my luck that my boss was an English grammar teacher before moving into engineering. My documents came back v... (more)

Book Review: The Incremental Commitment Spiral Model

Processes are not documented and reused by a set of individuals because they lead to failure. Like design patterns, they are documented and reused because they lead to success. They are all put together by very talented people who have successfully used them to develop software multiple times. For them the process is easy to use and understand. The teams that have not used it have a steep learning curve ahead of them. Just looking at the diagram of a pattern or process, definitely will lead you to failure every time. I have seen Waterfall, Spiral, RUP, OpenUP, and Scrum all fail ... (more)

Book Review: Agile Product Owner Secrets

When the agile movement re-cast the roles of the SDLC they did so with small projects as the baseline of their experience. A typical minimal SDLC method includes subject matter experts (those who execute the current workflow activities), a Project Manager, a Business Analyst, a Software Architect, UX specialists, Developers, DBAs, and Testers. A Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. The typical SDLC method responsibilities for activities, and the skills needed to get them done, went from 8 roles down to 3. For small projects that is gre... (more)

Android for Programmers and Android How to Program (2nd Editions)

This review is for two books. It is for Android: How to Program (2nd Edition) and Android for Programmers: An App-Driven Approach (2nd Edition) . Why? Because Android: How to Program (2nd Edition) includes the entire Android for Programmers: An App-Driven Approach (2nd Edition) book. Android: How to Program (2nd Edition) is in black and white and it also includes a Java language overview/reference. This book is great for the programmer coming from another language. Having the Java reference included as the second half of the book comes in really handy. Lately I have spent most of... (more)