The Mobile Development eMag brings together a selection of popular mobile development articles recently published on InfoQ.com. Learn strategies and best practices for developing native, HTML5, and hybrid mobile apps, see the results from the InfoQ cross-platform mobile tools survey, and gain perspective on the future of mobile development.
Scrum, arguably the fastest-growing Agile methodology, is well described in the original Scrum books, which tend to be read once and put aside. Scrum is a framework with simple rules. This Scrum Checklist will help you to remember these simple rules in the heat of daily work and stress. It enable you to create an enjoyable and productive work environment with your Scrum-Team.
Scrum packages proven product-development concepts in a simple framework, including real, cross-functional and self-managing teams, short iterative feedback loops, and lowering cost of change. These concepts increase agility, enable earlier ROI, and reduce risk. There are many concise descriptions of Scrum available online: This primer provides the next level of detail on the practices.
Though new Agile approaches, like “Lean startup” and Kanban, are emerging Scrum is still the most popular method used for Agile delivery and transition. "Real Life Scrum" contains the most typical problems teams and organizations encounter when adopting Agile and Scrum. It is NOT about finding THE right answer, but aims to highlight common problems, solutions and tradeoffs teams face.
Written by the agile coaches of Agile42, Agile Transition shares fundamental knowledge to support the observations & conclusions that the authors have identified within organizations transitioning to a more agile approach to work. The authors share their failures and learnings in organizations transitioning to embrace agile, and they share their experiences of what is required to succeed.
THE CULTURE GAME is a tutorial & reference for creating lasting business agility in organizations. This book provides you with specific tools & techniques to help teams (and the entire enterprise) rapidly respond to change, and describes 16 patterns of team-learning behavior, distilled from Agile software development, and provides the tools to socialize these ideas throughout your organization.
This mini book is for anyone struggling with a high daily workload, often juggling several projects at once. Pillars introduces you to the world of personal effectiveness and through simple steps help you get a better sense of importance, optimize your focus and improve your workflow in order to achieve more value. The tools used are a combination of Personal Kanban and The Pomodoro Technique®.
This book provides a set of essential thinking tools for understanding Agile adoption and transformation: how they differ and what you need to know to avoid being another statistic in the widespread adoption failure. In particular, you will learn how to use culture to work more effectively with your organization.
This mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system.
Scrum and Kanban are two flavours of Agile software development. So how do they relate to each other? Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement.Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.
For those getting started with Agile, this book offers a detailed first-person account of how one Swedish company implemented Scrum and XP with a distributed team of 40 people, and how they continuously improved their process over a year’s time.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them.