We are upgrading the repository! A content freeze is in effect until November 22nd, 2024 - no new submissions will be accepted; however, all content already published will remain publicly available. Please reach out to repository@u.library.arizona.edu with your questions, or if you are a UA affiliate who needs to make content available soon. Note that any new user accounts created after September 22, 2024 will need to be recreated by the user in November after our migration is completed.
A LESSON IN CONFLICT MITIGATION: INTEGRATING DIVERGENT DESIGN PHILOSOPHIES
| dc.contributor.advisor | Kosbar, Kurt | en |
| dc.contributor.advisor | Mormile, Melanie | en |
| dc.contributor.author | Brinker, Katelyn R. | |
| dc.contributor.author | Marcolina, Rebecca C. | |
| dc.date.accessioned | 2017-06-20T15:55:58Z | |
| dc.date.available | 2017-06-20T15:55:58Z | |
| dc.date.issued | 2016-11 | |
| dc.identifier.issn | 0884-5123 | |
| dc.identifier.issn | 0074-9079 | |
| dc.identifier.uri | http://hdl.handle.net/10150/624247 | |
| dc.description.abstract | The Mars Rover Design Team is dedicated to building a next generation rover that will one day assist astronauts in the field. The complexity of such a project increases when the two conflicting design philosophies of agile software development and traditional waterfall development must work in tandem in order to design and construct a rover within a year. Agile software development promotes the flexible, testdriven production of coinciding design aspects, while the waterfall design philosophy relies on thorough planning and rigid, sequential design schedules. The project managers of the team work to balance these opposing philosophies by fostering individual interests, allowing team members to select their own focus areas within a wide variety of mission critical tasks. This practice accelerates the design and construction of the rover and in turn creates the momentum needed to achieve a common goal while consolidating both agile software and traditional waterfall development. | |
| dc.description.sponsorship | International Foundation for Telemetering | en |
| dc.language.iso | en_US | en |
| dc.publisher | International Foundation for Telemetering | en |
| dc.relation.url | http://www.telemetry.org/ | en |
| dc.rights | Copyright © held by the author; distribution rights International Foundation for Telemetering | en |
| dc.rights.uri | http://rightsstatements.org/vocab/InC/1.0/ | |
| dc.title | A LESSON IN CONFLICT MITIGATION: INTEGRATING DIVERGENT DESIGN PHILOSOPHIES | en_US |
| dc.type | text | en |
| dc.type | Proceedings | en |
| dc.contributor.department | Missouri University of Science and Technology | en |
| dc.identifier.journal | International Telemetering Conference Proceedings | en |
| dc.description.collectioninformation | Proceedings from the International Telemetering Conference are made available by the International Foundation for Telemetering and the University of Arizona Libraries. Visit http://www.telemetry.org/index.php/contact-us if you have questions about items in this collection. | en |
| refterms.dateFOA | 2018-06-16T09:46:17Z | |
| html.description.abstract | The Mars Rover Design Team is dedicated to building a next generation rover that will one day assist astronauts in the field. The complexity of such a project increases when the two conflicting design philosophies of agile software development and traditional waterfall development must work in tandem in order to design and construct a rover within a year. Agile software development promotes the flexible, testdriven production of coinciding design aspects, while the waterfall design philosophy relies on thorough planning and rigid, sequential design schedules. The project managers of the team work to balance these opposing philosophies by fostering individual interests, allowing team members to select their own focus areas within a wide variety of mission critical tasks. This practice accelerates the design and construction of the rover and in turn creates the momentum needed to achieve a common goal while consolidating both agile software and traditional waterfall development. |
