InfoQ Homepage Methodologies Content on InfoQ
-
Scrum-ban Paper Adds Kanban to Scrum
Corey Ladas has written an interesting paper titled "Scrum-ban" in which he describes how a Scrum team might introduce the lean practice of kanban. He goes on to describe an evolutionary process, which if taken far enough, replaces most of Scrum. Even for those who don't want to scrap Scrum and go lean, the paper provides a useful view into what kanban is and how it can augment Scrum.
-
The Industrialization of Software Delivery
IT has consistently failed to deliver expected value time and time again. According to Ian Thomas, Industrialization (componentization, specialization) may be a solution for supporting software agility and reliability in the new business environment.
-
Presentation: Lessons Learned from Architecture Reviews
In this presentation, Rebecca Wirfs-Brock presents some practical lessons she has learned from doing architectural reviews. Many times projects are not delivered in time, or have quality problems or have an incomplete set of features due to architectural flaws. The reviews are meant to highlight existing risks and strengths of the architecture, and to reveal issues initially neglected.
-
Agile Coaches Attend First AgileCoachCamp
An Agile Coach is someone who helps a team, or an entire organization, adopt and improve their agile practices. AgileCoachCamp, held this spring in Ann Arbor Michigan, was the first ever conference specifically for agile coaches. The participants, who came from as far away as India, Sweden, and Ukraine, self-organized to put on more than 60 sessions during the open space conference.
-
An Introduction to Lean Thinking
Lean software development, which we hear a lot about these days, may be still a bit of a mystery for people who come to Agile via Scrum or XP. Earlier this year, at an Open Party was sponsored by InfoQ China, Ning Lu of ThoughtWorks China offered an introduction to Lean thinking, and said the biggest obstacle to Lean thinking can be the manufacturing mindset.
-
The Personal Retrospective – Improving Your "Wetware"
Andy Hunt's interview last month talks about his progression from pragmatic programmer to Agile development to his latest interest – Pragmatic Wetware. "Wetware is the stuff in your head. That's the thing between your ears that's really where all the action is – that's where all the software development actually takes place."
-
Opinion: When Designing Your SOA - Taste is Everything
Dan Creswell claims that "taste is everything" when it comes to putting together the pieces that make a good SOA. Dan says that picking the technology stack for distributed services, how you layer the service "units", etc, are a matter of taste as well as consideration of a number of guidelines, as opposed to just taking a cookie cutter approach to SOA as some seem to claim is possible.
-
Introducing the ALT.NET Podcast
InfoQ learned about a new podcast recently called the ALT.NET Podcast. This podcast focusing on the community of developers brought together who represent what is ALT.NET. Folks should remember the ALT.NET term coined by David Laribee.
-
Don't Worry About Scaling Scrum
Most Scrum adopters have their first doubt in terms of its scalability. Tobias Mayer suggests that before looking into quick solutions for complex problems, adopters should focus on understanding the principles of Scrum. Once the foundation is correctly laid, Scrum will take care of scaling itself.
-
Stories of Scrum Adoption in China
This recent inquiry, by InfoQ China editor Jacky Li, looked at five very different cases of Scrum adoption in China, which got different results. He asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.
-
Interview with Joseph Pelrine: Agile Works. But HOW?
Joseph Pelrine has come full circle: from university studies in Psychology, journeying through SmallTalk, XP and Scrum, and now back to broader questions: Why and how does Agile work? In this interview, Joseph talked about Complexity Science, and how story-telling, "sense-making," network analysis and speed-dating's gut-feel approach may prove more useful than our old toolkits for managing teams.
-
IBM's Smart SOA Vision Explained at Impact
At IBM's Impact event this week, IBM execs re-affirmed the view that the main innovation presented by SOA is business/IT alignment. They presented a business-process centric view of how SOA is an enabler for enterprises to change (agility), as well as their view of Smart SOA, a set of principles / maturity model for SOA based on numerous customer SOA deployments.
-
MomentumSI Releases new SOA Framework
MomentumSI released yesterday its SOA Framework -Harmony. It contains 5 perspectives which include Lifecycle, Governance, Technology, Maturity Model and Information Model. A SOA Framework is typically used to structure the organization, processes, activities, metadata... deployed for service construction.
-
Bedtime User Stories: Cowboys and Fairytales
In which David Longstreet claims Agile Software Development is a Fairy Tale that just tries to legitimise Cowboy development, and Geoff Slinker invites him to write a Serious Article based on Logical Arguments and Citing Sources.
-
Overburdened Teams are Less Likely to Root Out Waste
Sometimes, management encourages adoption of Agile but fails to help remove the overburden that cripples teams and keeps them in non-productive patterns. In his article, Roman Pichler looks at the "3 M's" of Lean, and how the concept of removing "muri" (overburden) provides help for Agile adoptions, by encouraging teams to give up wishful thinking and commit to their actual capacity.