InfoQ Homepage Project Management Content on InfoQ
-
Is it Time to Stop Estimating User Stories?
Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?
-
Application Lifecycle Management in Team Foundation Server 11
Team Foundation Server 11 has added many features in the area of Application Lifecycle Management. Some of the highlights include support for code reviews, iterations/sprints, resource allocation, third part testing frameworks, and a much more capable dependency graph.
-
Thoughtworks Technology Radar July 2011
ThoughtWorks recently published its Technology Radar; a report to help technology leaders understand emerging technologies, identify strategic platforms and tools and prepare their organizations for them.
-
Proposal for Eclipse-based Requirement Modeling Framework Released
Recently, a proposal for the Requirements Modeling Framework (RMF) has been officially released by eclipse.org. Vision is to have at least one clean-room implementation of the OMG ReqIF standard in form of an EMF model and some rudimentary tooling to edit these models.
-
Nailing Down Non-Functional Requirements
Non-Functional requirements are often associated with the state of the system and not with the functionality that the system has to offer. General 'ilities' of the system such as scalability, interoperability, maintainability, portability, performance and security fall under this umbrella. Agile teams usually struggle with defining and estimating the non-functional requirements in their projects.
-
New Books on Software Architecture
Software Architecture is one of the important topics for software engineers, because many failures of software development projects are caused by inadequate design. Thus, it is essential to learn more about architectural issues in theory and practice. Interesting new books that have been published recently or in the near future could be very helpful
-
PMI Agile Certified Professional Body of Knowledge
There is no single central reference for those seeking to prepare for the new Project Management Institute - Agile Certified Practitioner (PMI-ACP) test; instead the PMI provides a list of test areas, and reference books, which taken together constitute the body of knowledge for the certification.
-
Do We Need an Iteration Zero?
There are usually multiple things which need to be done before the start of a project. Teams usually use 'Iteration Zero' to put all necessary systems in place in order to start delivering business value in subsequent iterations. Is this the right way?
-
PMI Agile Certification Pilot Starting
Early adopters who want to be among the first to earn the new PMI-Agile Certified Practitioner (PMI-ACP) designation can apply starting May 23rd for the PMI Agile Certification pilot. Those selected for the pilot will need to take and pass a multiple choice exam on Agile fundamentals to receive the PMI-ACP certification.
-
Agile Leaders Weigh in on PMI Agile Certification
Scrum co-creator Ken Schwaber welcomes PMI's establishment of its own Agile certification program, and has recently posted his thoughts.
-
Visual Studio vNext Will Bring More Agility and DevOps Integration
Microsoft has unveiled at TechEd North America 2011 some of the new features coming in Visual Studio: more Agile tools for project planning and collecting stakeholder feedback, a connector for providing operations feedback to developers, plus architecture diagrams and unit testing for VC++.
-
Representing Agile Testing
Several members of the Agile community describe different styles for expressing user story tests and the testing of an entire theme.
-
How To Split User Stories
Many new Agile teams have difficulty splitting their user stories small enough to work well with Agile techniques. In several articles, members of the Agile community provide guidance on how to split user stories effectively.
-
The Further Value of Collapse
Mike Burrows started a discussion on the Kanbandev group which has led the community to explore the Expand / Collapse pattern. The discussion was covered elsewhere on InfoQ, in an article which followed the viewpoints of many practitioners who see more value in expansion than collapse. However, many people found both aspects of the pattern useful.
-
The Value of Collapse?
Agile methods recommend decomposing ("expanding") features into many small user stories. After the code has been written, however, should we collapse these small stories back into the original feature so we can deal with them all as a unit? Are there any advantages in doing that collapse, and if so, what are they?