The Latest
After Ten Years: One Person's Stance on the Agile Manifesto[article] In his CM: The Next Generation Series, Joe Farah often writes about ALM relative to agile. In this article, he lays out his views on the Agile Manifesto specifically. From collaboration and clear communication to the focus on individuals over tools, Joe covers what works, and what he thinks could work better. |
||
The Challenges of DevOps in the Enterprise[article] Many small teams are successful at implementing DevOps practices such as continuous integration. However, enterprises may find implementing DevOps best practices to be much more challenging. This article will help you understand how to be successful implementing DevOps in the enterprise. |
||
CM and ALM for Global Software Development[article] In his CM: The Next Generation Series, Joe Farah writes that there are many reasons that organizations or government agencies use distributed development. Whatever the reason, a software development team, and indeed the entire product team, needs to do all it can to ensure that development proceeds smoothly.
|
||
Essential Methods for Agile Project Success[article] Mark Balbes presents a framework for agile project management’s critical techniques. These techniques are required for successful agile development, where rapid requirements changes can be followed through with rapid development changes. |
Mark Balbes
November 12, 2012 |
|
Don’t Bury the Survivors: The Value of Clear Communication[magazine] Whether you’re discussing software defects with your test team, analyzing requirements with your BA, or programming in your favorite new language, communication is essential. Lanette Creamer has some tips to help you communicate clearly with any audience. |
||
Where Are the Interns?[magazine] The demand for software engineers is outpacing the supply from colleges and technical schools. Learn how to attract new talent through internships. |
||
Context Is King[magazine] A letter from the Better Software magazine editor. |
||
Which Visual Models Do You Recommend for Test Design?[magazine] In this installment of FAQ, SQE Trainer Rob Sabourin answers one of the questions students ask him most often. |
||
Journey to Agility: Leading the Transformation[presentation] How far can you take agile within an organization? Is it enough to just focus on agile development practices such as Scrum and XP or is something more needed? Agile is much more than just a development methodology. |
Skip Angel, BigVisible Solutions
|
|
Implementing Agile in an FDA-regulated Environment[presentation] While many industries have adopted agile, the medical device industry, which develops products for life-critical applications-where quality and reliability are clearly a top-priority, remains largely stuck under the “waterfall.” Medical devic |
Neeraj Mainkar, Neuronetics
|
|
Collaboration Workshops: Discover, Plan, and Prepare the Product Backlog[presentation] To deliver high-value products, your agile team must reach a shared understanding of prioritized stakeholder needs. Collaborative techniques are best for this type of work, but not all agile teams use them or use them efficiently. |
Ellen Gottesdiener, EBG Consulting, Inc.
|
|
Restating Scrum: Refining and Extending the Framework[presentation] Knowing the rules of chess doesn’t equip you with strategies to win the game-much less make you a chess master. |
Rob Maher, Scrum.org
|
|
Performance Appraisals for Agile Teams[presentation] Traditional performance evaluations, which focus solely on individual performance, create a “chasm of disconnect” for agile team members. |
Michael Hall, WorldLink, Inc.
|
|
Lessons from a DevOps Journey[presentation] In large financial institutions, treasury departments-specialized teams of traders and experts in liquidity, risk, accounting, financial forecasting, and quantitative analysis-manage the organization’s wealth and financial risk. |
Matt Callanan, Independent
|
|
Ready, Really Ready, and Really Really Ready Stories[presentation] Product owners create stories they believe are ready for development. Developers accept and then estimate stories that are not really ready to be started. |
Ken Pugh, Net Objectives
|