KADOS is web-based tool for managing SCRUM projects and other Agile projects
It allows teams to manage their projects through multiple dashboards on which they can pin e-postit for User Stories, Tasks, Risks, Problems, Notes, Actions etc…
KADOS has been build by a PHP team to replace the Excel Product Backlog of SCRUM projects.
This team has an old and deep reluctance to use Excel files as project management tools and has been tempted to use other quite efficient SCRUM tools, but they were Java tools.
After a few queries in SourceForge and other Free Software repositories, the team was unable to find a decent PHP SCRUM tool alive.
Then, the team decided to build its own tool and after a few releases to stabilize the software, the team published it as a Free Software.
Its particularity is to provide maximum screens where the user can move his post-it to change one of the attributes of the post-it
Kados supports most aspects and artifacts of SCRUM method, but it can also be adapted for other agile methods.
Kados is available in French and English version : each user can choose the language.
It is published and updated by Marmotte Technologies
Download it here: http://www.kados.info/en/?page_id=68
Proposed by: Aymar de la Montagne
This model is based on a simple questionnaire that contains ten questions. Each question is multiple choice, and each team member is expected to pick the option that he or she believes resembles the behavior of the ScrumMaster.
And Here are other presentations by Braintrust:
- Agile Project Management
- Scrum and Kanban
- An owerview of agile
- Agile secrets revealed
- and more…
Jim Benson is CEO of Modus Cooperandi, a collaborative management consultancy in Seattle, Washington. After being steeped in Agile for many years, Jim started working with Kanban and Lean thinking in 2005. In 2008, he started taking this idea further with Personal Kanban, which brings flow based work to the individual and team. Since then he has been integrating Agile and Lean into his work with his own software company, as well as clients like the United Nations, British Telecom, NBC Universal, and the World Bank. Here is a podcast from Software Engineering Radio. In this episode the guest host Marcel van Hove talks with Jim about Personal Kanban, about which Jim has recently co-authored a book together with Tonianne DeMaria Barry.
Many people find it easier to understand and retain concepts by seeing clear and compelling visual representations rather than just text. There are many existing pictures of Scrum and agile concepts, but they are all drawn differently and therefore a presentation or book composed from them would look disjointed or hacked together.
The Visual AGILExicon® is a way of describing core Scrum and agile concepts in a graphically rich and visually appealing manner. The pictures in the Essential Scrum book and Innolution’s training classes are based on this new visual lexicon.
You can browse and search the Visual AGILExicon here.
Quick Start Guide to Essential Scrum is a free PDF version of “Chapter 2, Scrum Framework,” from the book “Essential Scrum: A Practical Guide to the Most Popular Agile Process”.
In 16 pages, the “Quick Start Guide to Essential Scrum” provides a single-source, end-to-end visual overview of the Scrum framework, including its roles, activities, and artifacts. It gives everyone involved with Scrum, from the Scrum team members to those with whom they interact in the organization (including managers and executives), a common understanding of Scrum. It introduces the core concepts along with a clear, visual vocabulary for discussing them.
One important aspect that distinguishes the Quick Start Guide to Essential Scrum from other commonly available Scrum overview documents is its use of the new Visual AGILExicon®, a language for describing and communicating core agile and Scrum concepts in a graphically rich and visually appealing manner. You can learn more about the Visual AGILExicon at www.VisualAGILExicon.com.
Here, you may find couple of useful articles about Scrum and Agile software development. They provide insights into development processes and philosophies from industry experts that you might want to consider when developing your software or working as a team on a software project. Not only useful for .NET developers, but also for everyone who is interested in agile.
- Agile Principles and Values, by Jeff Sutherland. Jeff Sutherland provides an overview of the Agile principles as defined in the Manifesto for Agile Software Development.
- Ten Year Agile Retrospective: How We Can Improve in the Next Ten Years by Jeff Sutherland. Ten years after the publication of the Agile Manifesto, Jeff Sutherland describes the successes of Agile and pinpoints four key success factors for the next ten years.
- Done and Undone by Ken Schwaber and David Starr. Delivering a done increment is critical to being successful with agile software development. Using both real-world and theoretical examples, the authors demonstrate the difference between perception of “done” and the reality of “done,” and how that affects the success of a project. Using these examples, the authors go on to demonstrate tools and strategies that can help teams start with a definition of done that makes sense for them, and methods to help teams communicate dependencies, status, and the meaning of “done.”
- Building and Managing the Product Backlog by Mitch Lacey. A good product backlog is at the heart of any well-functioning agile team. In this article, Mitch Lacey explains the importance of a product backlog, describes what makes a good backlog, and provides some best practices for creating and maintaining your backlog.
- Prioritization by Mitch Lacey. In this article, Mitch Lacey discusses three methods that have proven very beneficial for many Agile teams: the Kano Model of Customer Satisfaction, a series of Innovation Games by Luke Hohmann, and Karl Weigers’ Relative Weighting model. He describes how any of these methods can help you move from rough prioritization of your backlog to a precise ordering that satisfactorily weighs risk, importance, and customer satisfaction.
- Estimating by Mitch Lacey. Mitch Lacey discusses the difficulty surrounding software project estimation, and provides tips and tricks for using two agile software estimation techniques when teams are estimating projects.
- Sprint Planning by Mitch Lacey. Sprint planning does not need to be challenging. In this article, the author provides examples and strategies for keeping sprint planning focused and effective, and detail potential solutions to common problems teams encounter when planning a sprint.
- Effective Sprint Retrospectives by David Starr. Going beyond techniques, this article offers ways to maintain and improve the practice and results of Retrospectives.
- Distributed Scrum by David Starr. Distributed teams often struggle with consistent, timely, and effective communication. In this article, David Starr explains how Scrum offers a container in which different types of distributed teams can improve and succeed.
Lean and CMMI
- Lean Software Development by David J. Anderson. David J. Anderson describes Lean Software Development, its history, and how it can be used by software development project teams.
- CMMI Principles and Values by David J. Anderson. The concept that an organization can be appraised at a particular maturity level and that this is an indicator of capability to deliver reliable work to the government is a matter of ongoing debate. In this article, David J. Anderson makes a case for Capability Maturity Model Integration (CMMI) and describes how it provides valuable insights for managers, process engineers and all external stakeholders including customers, investors, governance bodies and auditors.
- The Lean of Scrum by David Starr. In this article, learn about the inherent Lean qualities of the Scrum framework along with various ways to help Scrum Teams improve using Lean Thinking.
- Microsoft Solutions Framework (MSF) Overview . In this article, learn about the Microsoft Solutions Framework (MSF), an adaptable approach for successfully delivering technology solutions faster, with fewer people and less risk, while enabling higher quality results.
- Application Analytics: What Every Developer Should Know by Sebastian Holst. In this article, Sebastian Holst discusses the objectives and advantages of application analytics.
- Exploratory Software Testing by James Whittaker. In this article, an excerpt from his book Exploratory Software Testing: Tips, tricks, tours and techniques to guide test design, James Whittaker discusses goals, advantages, and approaches to exploratory software testing.
John Kotter comes with a model of change management which Oliver Lafontan has found inspiring, and that might inspire others too. He has written a number of books on the subjects, which in essence explain his 8 Step Change model in various formats and depth. When considering the introduction of Agile within an organisation, one might consider using the overall Kotter Change Management framework.
In this model, one first tries to identify the Problem or Opportunity they are trying to tackle and create a Sense of Urgency for it. Agile might presents itself as a solution later, the solution might be something entirely different. Kotter’s model allows to track that – from an organisation change management point if view – the new approach will be introduced with the best chances if success. In order to do this, he proposes the following 8 steps for introducing change within an organisation:
- Establish a sense of urgency
- Create a guiding coalition
- Develop a vision and strategy
- Communicate the change vision
- Empower broad based action
- Generate short term wins
- Consolidate gains and produce more change
- Anchor new approaches in culture
As already mentioned, this model works for any type of change, in our case, we are talking about changes that want to introduce Agile within a company. Introducing Agile in itself will also come with some challenges, and the introduction of certain practices, their monitoring, the effort put on coaching, will also require their own form of planning, execution, tracking and learning.
So what is this tool then? Well, it comes in the form of decks of cards. Each card in these decks represent an Acceptance Criteria for moving one notch closer to the desire behaviour or result. Why does he say decks? Because there are more than one of them, although using them in conjunction is effectively the tool he is proposing.
Here you can find more about these decks and download them:
Written by the agile coaches of agile42, Agile Transition shares some fundamental knowledge to support many of the observations and conclusions that the authors have identified within organizations that have transitioned 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.
Download this book FREE (PDF)
Table of Contents
- Understanding Agile
- The Agile Manifesto
- Empirical vs. Defined Process Control
- Pull vs. Push System
- Lean Thinking
- Why is this Relevant for an Agile Transition
- The Art of Balancing Freedom with Guidance
- Understanding Where You Are, and What You Want to Be
- Management Changes Required
- Start by Assessing the Current Situation
- Define a High-Level Strategy to Set a Clear Direction
- Why Agile Cannot be Bought
- Focus on People
- Embrace Change, but Avoid Chaos
- Appendix, Citations, Bibliography
Kanban takes an organization’s current development process and provides greater visibility into the status of the work and how it is proceeding. Kanban provides a method to continually adapt in order to smooth out kinks in the arrival of new development work. Kanban also gives more precise direction on how to invest development energy into only the most valuable work. This DZone Refcard provides you with an introduction to Kanban and how it can be used for Software Development. Learn about the Kanban Method and topics such as coordination practices, emergent behaviors, prioritization and more.