InfoQ Homepage Culture & Methods Content on InfoQ
-
Book Review: ATDD By Example
“ATDD By Example” value proposition was to be an introductory hands-on guide to implementing and successfully applying Acceptance Test Driven Development (ATDD) from zero. Despite doing a reasonable job of summarizing and/or pointing to several test-related practices required for any successful agile tester, the book ends up trying and failing to be all things to all readers.
-
Tradeoffs: Giving up Certainty
While organizations operate under an illusion of certainty, tradeoffs are inevitable. Giving up certainty does not mean giving up predictability. This article examines four flow choices for software delivery and presents three choices for IT Delivery: Throughput, Flexibility and all out speed.
-
Why the Agile Project Manager is the Secret Sauce for Development Projects
The Agile project manager is sometimes referred to as the “secret sauce” for software development projects? Leo Abdala describes a recent development project at a Fortune 50 company where the Agile PM instilled confidence with and produced a value-generating product for the client
-
A Proposal to Enhance the UML Notation
Raul Rugiero proposes an enhancement to the UML notation whereby requirements and test cases, in particular acceptance tests, are strictly related. Agile methodologies highlight this aspect basing themselves on test driven approaches. The notation of UML use cases may be enhanced in order to allow enhanced UML tools to properly handle links between use cases and tests.
-
Why Agile Methods Work
There is great economic value in looking at software processes from an execution perspective to examine their strengths and weaknesses. Keeping this perspective in mind keeps us at a safe distance from abusing buzzwords like Agile methods without really understanding the underlying principles that make them work.
-
Key Takeaway Points and Lessons Learned from QCon San Francisco 2012
This article presents the main takeway points as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Tutorials, Keynotes, Architectures You've Always Wondered About, Big Data and Analytics, Continuous Delivery,Cross Platform Mobile, Dynamic Languages, Java Renaissance, Loose Concurrency & CAP Theorem Today, Mechanical Sympathy, NoSQL and many more!
-
Visualizing the Big Picture of your Agile Project
Agile is all about the whole team experience. We plan together, code together, test together, and retrospect together so that everyone in the team is all on the same page. However, once your project grows bigger, teams start to get lost in pile of user stories and it gets harder for everyone to see that same big picture. This article discusses various ideas to visualize this big picture.
-
Interview and Book Review: Essential Scrum
Essential Scrum by Kenny Rubin is a book about getting more out of Scrum. It’s an introduction to Scrum and its values, principles and practices, and a source of inspiration on how to apply it.
-
PaaS Is The Word
This article presents a transition path to Platform-as-a-Service for IT. An exploration of the steps from pre-virtualization or virtualization through selecting and operating a PaaS.
-
Book Review: The Scrum Field Guide
Mitch Lacey has written the book The Scrum Field Guide: Practical Advice for Your First Year in which he presents advice on how to implement many of the Scrum and XP practices. Shane Hastie from InfoQ reviewed the book and asked the author some questions about the approach. The publishers have made a sample chapter available for InfoQ readers.
-
Making Architecture Matter
In this article, authors describe how they used the corporate management system to communicate architecture requirements to all the architecture stakeholders in a large organization and how this transformation helped them achieve benefits like application and infrastructure stability.
-
The Prioritization Divide: With Numbers or Without?
While there are many methods that use stories as a means for prioritizing development, there's a basic divide that asks whether it should be done with numbers or without. There are arguments on both sides, but instead of examining these, people tend to fall into one side naturally. Once there, they can become quickly entrenched in the belief that the other camp is foolishly mistaken.