Object Oriented Software Engineering   View all facts   Glossary   Help

subject > person or group > team

team comparison table

Subject	work more efficiently	include	follow	slowed down by	make	have	re-inspect	affect by	be	is a subtopic of	consist of	understand	avoid	coordinate with	perform	add	size	have only goal	rush	has part	ensure	prepare for	assign to	work for	feel that	keep	organized as	work on	work faster	inspect
inspection team		a manager if there are not enough people to perform inspections in a small organization					documents or code that is changed more than 20% for any reason		effective and efficient	10.10 - Inspections	between two and five people (including the author)		getting tired		inspecting			finding defects			that all the defects in the log are resolved	inspections by studying the code or other documents prior to the meeting and coming prepared with a list of defects		more than two hours at a time, or for more than four hours a day	they are all working together to create a better document	logs of inspections				documents that are not ready
software development team	if it has skilled management and a mature development methodology that includes such things as quality assurance, risk management, and iterative development	at least two people capable of performing each role, so that if somebody leaves or is sick, the project is not paralyzed	guidelines found in process standards	following an ad-hoc approach poor access and rapport with the customers delays caused by slow or poor decision making many customers and users needing time to negotiate decisions and requiring compromises to satisfy everyone	mistakes if they are under intense pressure to deliver software by a certain date and these mistakes can actually end up delaying them	optimal team size for a given estimated development effort - doubling the size of a team will not halve the development time		a certain amount of deadline pressure	proud of evolving a high-quality product such that it continues to meet the needs of customers	1.4 - Stakeholders in Software Engineering		only the overall software architecture, the details of its own subsystem, plus the interfaces to related subsystems		other software development teams working on the same project		people to a team if it gets behind schedule, in the hope of catching up because the new people will take time to learn what has been done, and will require support from the other people in the meantime, slowing them down	such that the total amount of required knowledge and exchange of information is reduced			user interface designer			one subsystem of a larger project				a hierarchical manager-subordinate structure, as an egoless team, or somewhere in between	legacy system	if it has good access and rapport with its customers and users if the project has a single user or customer

Next person or group: organization    Up: person or group    Previous person or group: person