InfoQ Homepage Culture & Methods Content on InfoQ

Articles

RSS Feed

Newer Older

The Day I Became Unnecessary - Part 2

In the second of two articles Claudio Kerber talks about his experiences in team formation and collaboration and explains the process whereby he "became unnecessary" as the team he was working with built trust and cohesion through trust, shared knowledge and shared experiences. He examines the theoretical underpinnings and discusses ways in which servant leadership emerges.

Claudio Kerber
on Apr 09, 2012
Key Takeaway Points and Lessons Learned from QCon London 2012

This article presents the main takeaway points as seen by the many attendees who blogged or tweeted about QCon. Comments are organized by tracks and sessions: Keynotes, Tutorials, Architectures You've Always Wondered About, Agile Adoption, Big Data and NoSQL, Cross Platform Mobile, Highly-available systems, Java Platform (hard-core Java) and many more!

Abel Avram
on Apr 05, 2012
Commitment – Writing a Graphic Novel explaining Real Options

Building on their work on Real Options, Chris Matts and Olav Maassen are writing a graphic novel to explain the concepts and share their knowledge in the area. They discussed the novel, the process of producing it and the crowdsourcing model of funding with Shane Hastie from InfoQ. A sample chapter is available for InfoQ readers to download.

Shane Hastie
on Apr 05, 2012
Lessons For IT From The Early Days of the FBI

J. Edgar Hoover is a controversial name in history, but his experiences building and running one of the key intelligence agencies in the world are very applicable to running IT organizations today.

JP Morgenthal
on Apr 04, 2012
The Day I Became Unnecessary - Part 1

In the first of two articles Claudio Kerber talks about his experiences in team formation and collaboration and how empowerment, refinement and facilitation enable the free flow of knowledge and value across team members and how cohesion emerges in collaborative teams.

Claudio Kerber
on Mar 27, 2012
Verification and Validation for Trustworthy Software Systems

In this IEEE article, authors discuss a continuous verification and validation of complex and safety-critical software systems using techniques like statechart assertions, runtime execution monitoring, and scenario-based testing.

Thomas W. Otani Man-Tak Shing James Bret Michael Doron Drusinsky
on Mar 05, 2012
Communicate Business Value to Your Stakeholders

Often project leaders—even Agile project leaders—talk about their projects in terms of features. Yes, and what do features really mean for stakeholders? Features are what your system or process can do. Benefits are why people care. And benefits equal business value. Learn why and how to communicate benefits rather than features—and what it will mean for you, your team and your organization.

Jenni Jepsen
on Mar 05, 2012
Agile Development Team Charter

Project Charters have rightfully focused on scope & goals for the project. However, team members can be unclear on their roles, activities, and expectations. This is especially true for people new to Agile. The Agile Development Team Charter addresses this gap by reviewing the Agile Prime Directive, Incremental Innovation Statements, and Team Member User Stories to provide clarity and context.

Terry Bunio
on Feb 27, 2012
Interview and Book Review: The CERT Oracle Secure Coding Standard for Java

"The CERT Oracle Secure Coding Standard for Java" book covers the rules for secure coding using Java programming language and its libraries with the goal to help Java developers eliminate insecure coding practices that can lead to vulnerable code. InfoQ spoke with book authors about how the security rules discussed in the book compare to other security coding frameworks.

Srini Penchikala
on Feb 15, 2012
Pattern-Based Architecture Reviews

In this IEEE article, authors Neil Harrison and Paris Avgeriou discuss a pattern-based architecture review (PBAR) process to help with system-wide quality attributes. They also discuss how PBAR approach helps with agile practices like frequent releases, changes for user needs, and lightweight documentation. They illustrate the benefits of PBAR process with a real-world project.

Paris Avgeriou Neil B. Harrison
on Feb 14, 2012
10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor. The authors provide insight into the underlying causes of business value risk and provide ten tips on how to avoid them.

Chris Matts Olav Maassen
on Feb 07, 2012
Your Brain on Scrum

Status, Certainty, Autonomy, Relatedness, and Fairness are wired into the human brain. Michael de la Maza how the latest neuroscience findings support agile software development and that there are good brain-based reasons why agile is so effective.

Michael de la Maza
on Feb 02, 2012