97 Things Every Programmer Should Know is Done The book 97 Things Every Programmer Should Know: Collective Wisdom from the Experts is finally available, and the title is on the mark. |
||
Agile 2009 - Aslak Hellesoy - Cucumber Test Framework
Podcast
Bob Payne got the opportunity to not just meet, but record this podcast with Aslak Hellesoy, at the Agile 2009 Conference. Bob and Aslak discuss the usage of the cucumber framework to facilitate automated regression testing at the story level. |
||
Managing Successful Agile Build Management Teams While Agile methodologies have made tremendous advances in programming circles, build and release management teams have traditionally shied away from a “full agile” approach. In informal polling of Build Engineers, I found only one team outside of my own that ran an Agile shop; while there are many out there who do, there are tender points that need special consideration.
|
||
Create and Maintain Product Roadmaps Using Agile Principles Anupam Kundu describes an agile-enabled framework for product managers, project portfolio managers, and IT executives to develop and maintain a dynamic and flexible product roadmap. The product wing of the digital division of a publishing house adopted this collaborative framework to to charter their product roadmap and simultaneously enable their project team to see and understand the “big picture.” |
Anupam Kundu
February 9, 2010 |
|
The Truth about Practices and “Being” Agile-Lean A working definition of “practice” is: A practice is a common and adaptive approach for doing something with a specific purpose in mind. When “being” agile and applying a practice we are focused on value-added not the means. |
||
The Value of Concurrent Testing Concurrent testing is the concept that as software is being developed, it is also being tested. Concurrent testing can be done in several ways; one of the most common is to perform testing at the system level. As a development team completes coding requirements for an application or system, this required code becomes testable, while other team members can execute test cases against the completed code.
|
||
Agile Practitioners – Put Business Analysts to Work for You! The agile methodology, like many concepts, is based on an “ideal” setting or environment. In the agile domain this usually constitutes a 100% co-located team of generalists who have unfettered access to the primary business stakeholder. Working in an ideal environment makes sense when you are describing theory, but organizations can find this perfect environment unachievable due to basic business constraints: resource skill sets, location, and time allocation. These constraints present barriers to agile adoption, can hinder productivity, cause frustration amongst the team, and can lead to project failure.
|
||
Agile Performance Testing Approaching performance testing with a rigid plan and narrow specialization often leads to testers' missing performance problems or to prolonged performance troubleshooting. By making the process more agile, the efficiency of performance testing increases significantly—and that extra effort usually pays off multi-fold, even before the end of performance testing. |
Alexander Podelko
February 8, 2010 |
|
Grooming the Product Backlog The product backlog is the ultimate resource to making sure that your project sees the light of day, and of the highest quality possible. That is, as long as your backlog is given the attention it deserves, and needs. In this article we help you keep your backlog groomed to perfection. |
||
Helping Agile Teams Tip Towards Greater Emotional Maturity Teams at a tipping point Is there a transformational moment within a team when an individual shifts from behaviors that support only individual achievement to those that support team achievement? What observations can we make as leaders about the specific behaviors that help individuals turn towards their team and lean on behaviors that support the team? How can we nudge teams forward until these behaviors gain their own momentum? My experience in setting up agile teams to tackle complex, systemic problems has brought me to focus on the set of behaviors that are both markers and catalysts of emotional maturity. Emotional maturity matters for agile teams because it enables business value. Emotionally mature teams are resilient and innovative in the face of the setbacks and barriers that come along with complex problems.
|
Ellen Braun
February 8, 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 |