Agile
SFAgile 2012 is a three-day “unconference” that brings together practitioners from Lean software development, the LeanStartup movement, and Agile software development. It will feature a mix of crowd-sourced content that include workshops, talks, dojos, and open-space-inspired spontaneous sessions.
Code reviews are not typically viewed as part of a pure Agile process, but some of the technique's benefits, such as collective ownership, are in line with the Agile philosophy, and they can be conducted without slowing your project down. Here are some suggestions for adapting code reviews to work in an agile environment.
Sometimes a pure agile approach is not appropriate for a particular project — the important thing is getting the work done, not strict adherence to a process. Still, a non-agile project can benefit from the inherent values of agile, including strong team collaboration, prioritized, incremental development, and regular progress assessment and adaptation.
Agile projects incorporate a number of techniques that are not easily transferable to traditional waterfall projects. One technique is the estimation of the size of user stories with abstract story points, and the use of story points to determine how much work can be completed in an iteration.
This 19-slide deck is a companion piece to the Agile Distributed Teams research report from ProjectsAtWork. It is designed to help you leverage the report's key findings and recommendations to achieve the benefits of working with distributed agile teams in your organization.
Distributed project teams are a reality of today’s business world, and the ability to enlist them while upholding Agile principles can bring great advantages as well as real challenges. Our 38-page report looks at those challenges but focuses on the benefits of working with distributed agile teams — and how to achieve them.
Whether you're just getting started with Agile or expanding your Agile practice to include distributed teams, this report is for you. It provides meaningful data points and best practices from hundreds of practitioners and thought leaders in the industry. These findings have not been presented anywhere before, and go well beyond the numbers to give you best practice insights and real-world tips that you can apply now and in the future.
Retrospectives are a catalyst for continuous team improvement, providing a feedback loop to examine methods, teamwork and results. But holding monotonous retrospectives isn’t much better than holding none at all. Here are three techniques you can interchange for maximum effect.
Instead of measuring quality, Agile enterprises commit to it by investing in integration and testing, developing a common language around quality, and nurturing motivated, disciplined teams. Ultimately, quality reigns when organizations value it as much as profitability and protect the agile processes that support it.
Frustrated by project charter meetings that feature overly textual, often generic descriptions of what the team can expect and how to accomplish it, a project manager applied the agile concept of User Stories to better describe project interactions and inject more real-world meaning into a kickoff document.
Ty K: "Thanks for contributing to the blog Ojiugo. There are a lot of very smart PMs ou…" on Building Project Management Knowledge with Social Media
May 14, 2012
Ojiugo A: "Excellent article,these days experience is no longer the only teacher but great …" on Building Project Management Knowledge with Social Media
May 14, 2012
Ty K: "These are all great ideas. I think retrospectives are critical for any team, eve…" on Fresh Retrospectives
May 11, 2012
Anju A: "It pains a lot when some very common review technique are termed as "Alternate A…" on Agile Code Reviews
May 11, 2012