Kanban System Design Karl Scotland explains that viewing kanban as a systemic approach leads to systems thinking. Systems can be thought of as being made up of elements, which interact to meet a purpose. They are more than the sum of the parts, and the system’s purpose is crucial in determining the system’s behavior. |
||
Four Reasons Medical Device Companies Need Agile Development The waterfall style of development is so deeply engrained into the culture of medical companies that most can’t imagine anything else being used to develop software that has power over human life. However I argue that precisely because of patient safety, medical device companies in particular need to adopt agile practices. I’ve seen too many bloated medical device project fail or limp across the finish line for causes that can be directly linked to the waterfall method. Specifically: |
||
PRINCE2 and Agility: Reclaiming the Manifesto In October this year Codeworks DEV received the 2010 Agile Award for the “Best Use of Agile in the Public Sector”. The use of Agile Methods within large, publically accountable environments has long represented a challenge to the Agile community. Agility is more often associated with small to medium size enterprises (SME’s) in the private sector, where organisations are incentivised to keep pace with a changing business environment. Public sector companies and larger corporates, on the other hand, are renowned for their essentially prescriptive, “non-agile” attempts at long-term planning using techniques such as PRINCE2. |
||
Lessons from a Loudmouth I have a colleague whom I used to view as a loud mouth. He was intelligent, articulate and full of life, but also arrogant and opinionated. He never talked quietly; he shouted, hurling his voice across the room. One evening, he appeared just as several of us were leaving for dinner after a day-long meeting. I tried to send him go-away vibes, but he wasn’t in receive mode. When one of the others invited him to join us, he eagerly (and loudly) accepted. |
||
Thoughts from Mid-Project My team is in the middle of one of the hardest projects—we call them "themes"—we’ve ever tackled. We’re a high-functioning agile team that has helped our company grow and succeed over several years now—we “went agile” in 2003. Here’s one thing I know for sure: No matter how many problems you solve, new challenges will pop up. |
||
How to Resolve Disputes So Everyone Wins It's a special skill to be able to terminate disputes amicably. In this week's column, Naomi Karten offers suggestions for how to resolve disputes so that none of the parties suffers from black eyes or bruised egos. |
||
|
Software Project Estimation Tired of guesstimating your estimation process just to create a completion date management will accept? Jonathan Kohl takes the guess work out of estimations by focusing on uncertainties. It may sound counterintuitive, but the idea is to focus on the fact that all projects face unforeseen delays. The rigorous estimation process Jonathan describes here provides your team a way that ensures enough time is scheduled for development and a date for completion management can agree upon. |
|
Four Frequent Feedback-Gathering Flaws Giving your customers the opportunity to provide feedback is great, but only if you don't fall into one of the four traps that Naomi Karten describes in this article. Let your customers know that not only do you want their feedback, but that you'll actually use the important info they give you. |
||
Large-Scale Distributed Agile Teams – Creating, Sizing, Prioritizing and Grooming the Product Backlog Teams that work in large-scale, complex agile environments are often distributed. As a result, it is almost impossible to discuss distributed agile development without discussing the implications of working at scale. In this article, we will cover the following topics to help distributed, large-scale teams create their initial product backlog at the start of a project: |
||
How to Align Your Team with the Scrum Model 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 the model. Because, vanilla-Scrum only describe what the role does in the process. |
Vinay Krishna
November 9, 2010 |
Pages
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |