The development of medical devices has largely gone unchanged in the last few decades. It has only been recently that it and other heavily regulated industries have considered Agile.
When I work with clients who are looking to improve their Agile process, or when they need help to fix a Scrum problem, I usually start by looking at what I think are the big three pitfall areas of Scrum.
Recently I was caught off guard by a guy presenting his evidence that Scrum is only for software.
Despite their obvious advantages, some people are skeptical about stand-ups and do everything in their power to skip them.
Agile may be the most poorly comprehended word in the world of IT. So what is it?
Having spent most of my Agile life in a distributed Agile culture, I thought it time to write down some of my thoughts about distributed Agile setups.
With continuing New Year's energy, let's tackle an ongoing challenge in the product development and Agile world.
These are the three important phases that come to my mind when I think of maturing on the Agile journey.
I'm sure you've heard the saying "Practice makes perfect" sometime in your life. Experience has led me to believe that, despite all good intentions, this statement is not phrased correctly.
Scrum is more efficient when we have small teams that are colocated. So how do you manage when you work in a big program and have to manage multiple application teams?
Here is a game that can have a strong effect on building team cohesiveness.
What's the first thing that comes to your mind when you hear the word fragmentation?
It is important that technical debt is made visible to the team so they can act on it as required.
I was in traditional project development, where I played the role of a developer. When the organization started to transition to Agile and the structure was revamped . . . I was taken by surprise and had no clue about how all this would work.
While the items in the product backlog must be ordered, ordering by priority is only one of the many techniques -- and rarely the best one.
I was sitting in a wheel alignment shop few days back, waiting for my turn, and there were about six cars in the pipeline. My attention was caught by the way the three people, including owner of the shop, were working. . . .
The retrospective meeting serves as a way for the team to analyze itself and make up a plan of improvements. I will list some tips and tricks for an effective retrospective meeting. he retrospective meeting serves as a way for the team to analyze itself and, as a result, make up a plan of improvements for its benefit. - See more at: http://www.scrumalliance.org/cms/getdoc/418f5e42-85a6-4365-a66f-38cef6c58c65/SPRINT-RETROSPECTIVE-%E2%80%93-STRATEGY-%E2%80%93-TIPS-AND-TRICKS.aspx?viewmode=2&devicename=&lang=en-US&langobjectlifetime=request&loaddevice=1#sthash.O01sWCHl.dpuf
No one talks carefully about who should be on a Scrum team and who should not. In my opinion, this is one of the most neglected discussions in the Scrum world. no one talks carefully about who should be on a Scrum team and who should not. In my opinion, this is one of the most neglected discussions in the Scrum world. - See more at: http://www.scrumalliance.org/cms/getdoc/28eaf58d-26f3-49f3-b2e6-93fb0f7d66e3/The-composition-of-Scrum-Teams.aspx?viewmode=3&lang=en-US&langobjectlifetime=request#sthash.0D8QQ57v.dpuf
Different opinions among Scrum followers sometimes create points of discussion. Recently one such point was, "Who can terminate a sprint?"
Under the right circumstances, a new Scrum team can rapidly be taught just enough Scrum to kick off a real-world project in two and one-half days. This is like a car accelerating from zero to sixty in under six seconds!