As companies transition to Agile and Scrum to manage their software development projects, how does this affect the work of business analysts? Nancy Nee, VP Global Product Strategy at ESI International, shares her opinion on the role of business analysts in Agile software development projects and how this approach impacts the requirement gathering activity. She also provides some input on how to handle conflict between stakeholders.
This article gives you five tips how a clear practice with the support of tools will help teams be more successful in delivering done products when using an agile approach. Actually many tips will also be helpful for other methodologies and project approaches. This article uses Microsoft Application Lifecycle Management tools as an example, but the tips are valid for any other ALM tool suite.
As agile coach and department director I mentor my leaders on the virtues of “servant leadership.” Indeed, I consider myself a servant leader and use this as a guiding principle in how I lead my organization. This article introduces servant leadership and describes why it is critically important on agile teams. It contrasts “old school” autocratic management versus “new school” servant leadership by comparing a traditional PM to a Scrum Master.
The Scrum Burndown chart is very simple. It is easy to explain, easy to understand. But this metric also put in evidence some pitfalls observed in many agile workshops and adoptions. This article discusses them.
The Dialogue Sheet is a new technique for Agile team retrospectives. This technique involves a large sheet of paper that help to create good discussion and teamwork in Agile and Scrum projects.
Applying Scrum beyond the IT world can be a challenge, but isn't impossible. The learning and development standard of ADDIE is just one way Scrum can lead old methodologies to live in a new framework.
I have noticed an increasing trend that software development teams, venturing into agile world, do their first investment in Scrum training. Is it a wise investment? Does it provide a good rate of return?
This article proposes four ?smells? that might indicate that you?re not optimally practicing whole-team approach in your Scrum software development project.
This article is dedicated to the people endlessly discussing relationship between Scrum and Agile. Scrum is one of the biggest process invention but it does not guarantee success. Even creators of Scrum accept that more than half of the Scrum implementation does not go well. Why is that? Scrum is critical but what is more critical than Scrum?
Through a creative analogy, the following video helps you understand why we need to be careful with Scrum implementations. Here are the key learning objectives:
This article discusses several symptoms and causes of schedule flaws, presents metrics and diagrams that can be used to track your team?s progress against its schedule and describes Agile ways to address these risks.
This article presents the value of just-enough user-centered design in an Agile development process.
Taking advantage of Scrum practices is what makes a Scrum team succeed. After all, the development term ?Scrum? was derived from rugby for a reason. The name Scrum was chosen to represent specific software development practices because like Scrum team in rugby, one team needs to cover a variety of responsibilities. This team works towards a common goal, continuously, in parallel, and under circumstances that could, and do, change rapidly.
There are a number of strategies and working practices available for Agile software development, I have included the process that works for me; this is based on my real life experiences working with stakeholders (more about these in a moment), developers and testers.
Ist Agiles Projektmanagement mit dem PMI® Gestaltungsrahmen und SCRUM komplementär möglich? Klar! (Sorry available in German)
One of the important, key Scrum practices is the Daily Scrum. It happens daily during each Sprint and the entire team participates.
During this Daily Scrum everyone answers the following three questions:
Often people treat it as a typical status meeting and behave very casually, which eventually could lead to bad results.
A successful scrum implementation requires proper understanding of Scrum processes within team and within all project stakeholders. Even after proper training and certification (CSM/CSPO) it?s really tough to achieve the success as intended. There is one common and important problem which has always been overlooked ? the alignment of current team with Scrum model. Because, vanilla-Scrum only describe what the role does in the process.
This article presents an experience report about mixing CMMI and Scrum in the same company.
This article presents what are the Scrum Product Owner activities and how he has to keep the balance of interests between the Scrum team and the other stakeholders.
A short article presenting some of the things I've learned as a leader.
This article contains five stories, mostly based on real life, that might help you see how Agile can become mechanical and what you should do about this.
Ein Projekt kann nur erfolgreich sein, wenn es über so viel Eigendynamik wie die Dynamik ihrer Umwelt verfügt.
Projekte reagieren permanent auf VerÃ¤nderungen in ihren Umwelten, indem sie sich von ihnen irritieren lassen. Wenn die projektinternen AblÃ¤ufe und das Auftreten den Umwelten gegenÃ¼ber viabel, d.h. brauchbar, sind, befindet sich das Projekt auf dem Weg zum Erfolg.
A brief article on taking the right decisions on technical matters.
Simple exercise for gaining a common understanding and consensus about what it means to you, the team and the organization to be Agile.
The modern world of Agile systems-software product development and delivery presupposes we work faster and better, do more with less, change continuously, and invent new ways of working. The modern formula for work appears to be:
People’s beliefs, understanding and perspectives as well as their unwillingness and ability to change makes being Agile hard.
Contributing to this challenge is a proliferation of new vocabulary, new terms, old terms having new meaning, guidance, books and articles on the subject and ones interpretation of what it means to be Agile.
Minimize frustration and waste usually associated with gaining consensus on what it means to an individual, team and organization to “be Agile” as they work through the forming, storming, norming and performing stages of team development.
This presentation makes understanding Agile & Lean Product Development and Delivery with SCRUM easy.
Somebody asked me an interesting question: what does a Product Owner do during the Sprint? But before answering this question, letâ??s go one step back and see what the PO does for the release backlog.
Mastering the "art" of agile/lean systems and software product development and delivery requires you ask yourself, "Do I really understand both the technical and non-technical imperatives associated with this undertaking?"
This article takes a look at mastering the art of agile/lean system and software product development and delivery; focusing on change.
Saying no to the team, to the client or the Scrum Master, is one of the PO's more important tasks, but let's think in some situations when this might happen
One of the main contributions from Scrum to the software development community is the conscience that has been created about obtaining a tangible deliverable product at the end of each sprint. In theory, the potentially shippable product should be ready for shipping at the end of each sprint, given that if you can find a client willing to buy a product that works with limited functionality.
Theory contradicts reality in many occasions because the team hasn't implemented enough functionality or this has not been completely tested to be considered as a valuable product that can be delivered to clients.
A technique for scaling Scrum up on larger projects...
A quick overview about Planning Poker Cards for Agile practitioners and some resources of physical and online versions of the tool
...but only when you're ready.
An overview for some of the Scrum tools used in development and management of software in general and under Microsoft environment in particular
Communication is one of the key factors that drive teams towards their goals, making possible the exchange of ideas, plans or problems. It is therefore crucial to do it efficiently, while keeping in mind that youâ??re still talking to humans and not some kind of information processing machines.
Some lessons learned from one of the tough sprints I managed
Here are examples of a Product Backlog and Sprint Backlog for use in Scrum...
Why Scrum wins in medium-large organisations...
Implementing Scrum can be hell!
Some useful resources for new Scrum Masters or Scrum Masters to be...
So you've had enough of failed projects. You like the sound of agile development as an alternative. You buy into the key principles and you're ready to take the plunge.
Which methodology should you go for?
Continuous learning comes as standard...
Easier said than done!
"oh dear, it was going so well"...
This is about each and every team member taking responsibility and reporting back to their peers...
How to handle a Sprint in Scrum...
How to handle a Sprint in Scrum...
How to handle a Sprint in Scrum...
A place for visibility and collaboration...
Breaking requirements into tasks and estimating...
How to plan iterations and gather requirements in Scrum...
You need to provide some high-level initial estimates, in order to get an idea of the size of your project or product backlog. How many times have you heard someone say, 'don't worry, I won't hold you to it'? Here's how to estimate your product backlog...
Getting started with Scrum...
Agile managers still need to lead...
How cam marketing keep up with rapid agile development
Running an agile meeting means an upfront investment of time with the pay back of better visibility of issues as they really are. This is part #2 in a 10 part series on the agile originations. Refer to - Agile Meetings For more details.
The marketing strapline for Scrum is "It's about Common Sense". If it's such Common Sense, why do so many development teams tend not to work this way?
Pain with a threatened ROI or pleasure with an improved chance of a greater ROI - which one appeals to you?
Implementing an agile development frame work, such as Scrum, does not solve your companyâ??s problems but helps identifies them.
In agile development, try to apply the 80/20 rule...
Agile software development is all about frequent delivery of products. In a truly agile world, gone are the days of the 12 month project. In an agile world, a 3-6 month project is strategic!
In Agile Development, requirements evolve, timescales are fixed...
Agile Development is all about small, iterative *releases*
How do you get your estimates just right to fit your Sprints perfectly? Answer: you can't. So how do you avoid finishing your Sprint early or disappointing your Product Owner?
10 Key Principles of Agile Development
Thoughts on the importance of basic rules in enabling emergent capabilities in Slime Molds and Software Development teams.
This article describes how the author helped her team successfully transition to Scrum by allowing the team to self-organize and discover solutions to their problems.
An article on using Scrum with the Unified Process.
In this article, Jeff Sutherland recounts the first Scrum project, which was at Easel Corporation in 1993. The article summarizes that first project and presents the lessons learned from it.
This is the very first article on Scrum describing its origins in Japanese new product development. The article is available only for purchase from Harvard Business Review for .
An initial collection of "smells" or indicators that something may be amiss on a Scrum project.
This paper describes the empirically generated set of rules and tools that allowed an existing IT operation to adjust their workflow in maintaining, enhancing, and supporting business demands - and to do this in a proactive, agile, manner.
Description of a highly successful agile project at Primavera.
We can read about agile processes in books and articles. This tutorial provides an overview of agile processes and describes them by difficulty of implementation - the skeleton, the sashimi, and the heart. How Scrum fleshes out each of these aspects of agile processes is then described. Since it is easy to think one knows what agile processes are like without understanding what they really feel like, two case studies are used.
A concise (one page) overview of the Scrum development process
A lengthy review of the book "The Knowledge-Creating Company," which is by the originators of the Scrum process, Ikujiro Nonaka and Hirotaka Takeuchi.
A short but good introduction to Scrum.
Excellent overview of all leading agile methods including Extreme Programming, Scrum, Crystal, Feature-Driven Development, Rational Unified Process, and DSDM.
This article describes how a project was successfully downsized from 100 to 12 developers. To make such a dramatic adjustment the development process was switched to Scrum and user stories.
An excellent presentation that describes the history of iterative and incremental processes and presents some of the theory underlying the Scrum process.
Brief description of a project in which XP and Scrum are combined.
Discusses how combining the best of some popular processes can provide a successful software development environment for your project.
Very early writing about Scrum and Scrum meetings. Interesting from a historical point of view, and to see that the fundamental Scrum principles haven't altered much over the past 6 years.
Good overview of agile with brief descriptions of Extreme Programming, Scrum, Crystal, and Adaptive Software Development.
This article looks at XP as a series of nested conversations occurring on the scales of monthly, weekly, daily, and more frequently.
Describes how the use of a daily meeting contributed to the success of a project.
Project Managers can learn from the new agile methods, too: Scrum and Extreme Project Management use close quarters, communication and discrete goal-setting to create highly effective project plans.
Explores the theoretical foundations of project management. Describes the Scrum process and how Scrum rejects the underlying theoretical foundation of conventional project management.
Jeff Sutherland is one of the originators of Scrum. In this article he retraces his experiences with Scrum in five very different companies.
Two page introduction to the concepts of Scrum. For those who are looking for a quick introduction, not for depth.
Rising and Janoff discuss their experience in implementing Scrum to address rapidly changing requirements.
Describes techniques that can be used to successfully introduce an agile process into an organization. Addresses concerns of programmers, testers, managers and HR departments.
Copyright 2003 IEEE. Reprinted from (IEEE Computer, June 2003). This material is posted here with permission of the IEEE. Such permission of the IEEE does not in any way imply IEEE endorsement of any of Agile Alliance's products or services. Internal or personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution must be obtained from the IEEE by sending a blank email message to email@example.com. By choosing to view this document, you agree to all provisions of the copyright laws protecting it.
Describes advantages of frequent, short meetings. Gives real-life experiences from Scrum projects and offers tips on how to conduct daily meetings.
Excerpted second chapter from the authors' book on Scrum. Describes how Scrum came into existence.
Scrum has defining moments when the concept of a self-organizing team becomes clear. This sidebar to Jim Highsmith's "Does Agility Work?" describes these epiphanies.
Informal, iterative methods fueled the successes of a health-care software company and a Singapore bank, but agility is no panacea. When analysis paralysis keeps good ideas from rising to the top, talent may be as crucial as process.
This article compares Scrum and XP and finds them synergistic. Experiences on a real project are described.
Poppendieck describes the class of problems known as "wicked problems" and provides software development examples. She gives advice about how to succeed against wicked problems and identifies Scrum as an excellent approach for wicked problems.
The Scrum methodology can pose a challenge for software testers who are used to more traditional waterfall-inspired development processes. Jonathan Kohl relates his experiences working on Scrum teams who found some clear advantages in changing their methods.
This article provides a basic overview of Scrum, an agile process for managing software development project.
Article about how game developer High Moon Studios won an award for their HR programs, organizational performance, and employee satisfaction. The console game industry is known for its employee-unfriendly cultures; High Moon Studios used the agile process Scrum to avoid the typical game-development culture while putting out hit games such as Darkwatch.