Service Design Pattern Book

Fantastic book on Service Design Pattern by Robert Daigneau
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services

Design Thinking – Drive continuous innovation in Agile teams

Design Thinking Introduction – Approach for driving Innovations in Agile teams?

What is Design thinking?

The term refers to a set of principles, from mindset to process,  practices and approches that can be applied to solve complex problems. It’s a structured approach to generating and developing ideas for continuous innovation.


Article from Tim Brown on Design Thinking

RedHat on Design Thinking

Videos:
http://www.youtube.com/watch?v=UAinLaT42xY

Books:

Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation by Tim Brown (Hardcover – Sep 29, 2009)

Designing for Growth: A Design Thinking Toolkit for Managers 

Design Thinking: Understanding How Designers Think and Work

Lean Software Development Books

Books on Lean software development:

Three books from Mary and Tom Poppendieck. I enjoyed reading all 3 of them.

1) Lean Software Development: An Agile Toolkit by Mary Poppendieck and Tom Poppendieck

2) Implementing Lean Software Development: From Concept to Cash by Mary Poppendieck and Tom Poppendieck

3) Leading Lean Software Development: Results Are not the Point by Mary Poppendieck and Tom Poppendieck


Management 3.0 – Jurgen Appelo’s fantastic book


I completed reading Jurgen Appelo’s fantastic book on Agile development.

This a good read for all development managers and agile practitioners. Very practical book which teaches models for agile team and organization development. Advice coming straight from someone who has worked in different roles, practiced and experimented with different agile development practices and models. Unlike management guru books, I found this book very practical, straight on the subject and valuable to development managers like me who want to learn more about softer aspects of agile product and team development.
Must read for all managers, leads committed  to improve the Software development practices in their respective organizations.

Jurgen discusses following 6 views.

Six views of the Management 3.0 model:

● Energize People
● Empower Teams
● Align Constraints
● Develop Competence
● Grow Structure
● Improve Everything

Management 3.0: Leading Agile Developers, Developing Agile Leaders (Addison-Wesley Signature Series (Cohn)) byJurgen Appelo 

Product Details

User Stories Driven Development

User stories driven development is great way to do agile development. No better way to get the User, Product owner, developers and QA getting engaged together into active conversation through out the development cycle. Though simple, the implementation for new organization can get really difficult. System, process and people doing traditional long detailed requirements docs driven development have to unlearn lot of old practices before adopting new agile concepts of User stories. Roles and  responsibilities of each stakeholders are always at conflict and development organizations  struggle to get it right the first time. My suggestion is get the Agile champion to infuse new agile ideas and concepts. 
Old timers will always oppose it. Product management will get their hands off from writing User stories which contain just enough details to initiate the conversation between team members. They will always crib about the time constraints. We can not blame them, as they have been trained in writing either detailed requirement docs or Use Cases behind closed doors before other team members actually get a chance see it. There are other practices which make proactive dialog between Agile team memebrs difficult. Developers have ego,  they think they can read any requirement doc and craft it into a product. QA will always test and break what developer has implemented. Real user requirements are lost in this cycle because therir is npo active feedback loop keeing them on track. Finally user get a system as per the stated requirements but not what they wanted. 
Mike Cohn’s book on User story driven development is is great read.