InfoQ Homepage Agile Content on InfoQ
-
What Are the Trends in Technology Today?
ThoughtWorks has released the Technology Radar 2010 this month, a white paper containing ThoughtWorks' technology strategy and trends in four major domains: Techniques, Tools, Languages, and Platforms. InfoQ looked at this whitepaper in depth to better understand the ideas and suggestions being offered by ThoughtWorks.
-
InfoQ User Survey - 11 Questions to Help Us
As an InfoQ reader, we have a small favour to ask of you; we’re trying to learn more about our members and we have a survey with 11 questions on it to help us in our content, redesign, and business efforts. We're interested in how you use the site, what type of content you find interesting, and more about your background. This survey is anonymous and your replies will be kept confidential.
-
Decoupling Your Application From Your Dependency Injection Framework
Dependency Injection has become a much more accepted and accessible approach in recent years, driven by many factors including increased popularity in SOA, TDD, and many other factors. With this has come increased usage of Dependency Injection frameworks. Bob Martin advises, with examples, applying a decoupling approach between your application code and your Dependency Injection framework.
-
How Does Your Agile Compare to Your Competition?
A lot of times teams and organizations would like to evaluate their way of working with their competition. They would like to focus on their areas of improvement and incorporate feedback to do better. Comparative Agility assessment is an assessment tool which suggests that the results would help guide the organization in planning the next set of their Agile initiatives.
-
Is Technical Debt a Technical Issue?
Is technical debt a purely technical issue that can be addressed directly by refactoring and tests or is it a symptom of a bigger problem? Will the adoption of TDD fix the issue or just cover up a symptom of something bigger?
-
QCon London in 2 Months: Skype, Facebook Case studies; QCon iPhone App
The 4th annual QCon London is just 2 months away! 75% of the schedule is now live including case studies from Facebook, Skype, sky.com, and dozens more. The next discount deadline to register expires tomorrow. QCon this year has an iPhone app! Search for 'QCon Guide' in the AppStore.
-
A Community of Thinkers
Jean Tabaka, Liz Keogh and Eric Willeke got together to contribute something to the "Lean Software and Systems Consortium". Instead they realized the Software Development Community (Lean, Agile, Kanban and well beyond) needed a help remembering the importance and value of true community.
-
You Can Say No to 'Pull' in Kanban
Kanban places a lot of emphasis on the pull psychology. Most people who subscribe to lean ideas prefer pull systems as opposed to traditional push systems as they are deemed to be superior for performance and productivity. However, there might be situations where you would want to say No to a pull.
-
Opinion: Agile Success Is Not Dependent on Agile Techniques
The marvelous successes of Agile teams in the past, present, and future are fact. But so are the failures: the cases of 'fragile' adoption, 'we suck less' adoption, and many other cases where Agile teams fail to produce great software and/or fail to effect the organization as a whole. Is this something that can be addressed and 'fixed' or is Agile development only useful for a some teams?
-
Adaptive Reuse - Lessons from civil engineering
Software engineers frequently take issue with the sequential development processes that are believed to be at the core of civil engineering – in answer to the “why can’t you build software like they build bridges” criticism sometimes levered at software development. The reality is that civil engineering projects frequently apply approaches that Agilists will recognise.
-
Agile Retroflection of the Day
Retroflection is a concept in which one substitutes self for environment, as in doing to self what one wants to do to someone else or doing for self what one wants someone else to do for self. Introspection is a form of retroflection that can be pathological or healthy. Based on a similar concept Yves Hanoulle started the Agile Retroflection of the day project.
-
Minibook: Scrum and Kanban: Making the Most of Both
Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The new InfoQ minibook by Henrik Kniberg and Mattias Skarin, Kanban and Scrum - making the most of both, clears up the fog so you can figure out how Kanban and Scrum might be useful in your environment.
-
Estimating Business Value
The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value. The concept is simple, but implementing it well relies on having a mechanism to assess business value. Pascal Van Cauwenberghe has recently described an approach to defining business value, called "Business Value Modeling", which may help.
-
Overlapped or Synchronized Sprints?
When a Scrum project grows, so do the team members. The suggested way of managing a growing team is to split the team into multiple teams keeping in line with the Agile recommended team sizes. However, there could be multiple communication and coordination problems when each team starts working in a sprint of their own.
-
Reasons for Delay in an Agile Project
A delay, in general, is getting something done later than it was scheduled for thereby causing distress and inconvenience. Likewise, a delay is considered to be a waste in the Agile terminology. A delay causes discontinuity and thereby causes other wastes like relearning, task switching etc. A few Agilists discuss the common delays and ways to resolve them.