The final presentation for my Project Management class. I led my project team through the planning, execution, and closure phases of our project.

1. The A-Team
Sean O’Hara
Brittney Mumma
Robert Lee
Edward Buchanan

2. Project Definition
Initial
This team is ultimately creating a remote controlled robot that will be able to move straight forward, straight
backward, left, and right. The robot will also be able to open and close a section of its body to flip over objects
in its way. In addition, the project should include instructions for kids and adults alike to build their own robot.
Actual:
This team created a remote controlled battlebot that is able to move straight forward, straight backward, left and
right. The robot is also able to open and close a section of its body to flip objects in its way. We were not able
to create and include instructions for kids and adults to build their own battlebot due to time and budget
constraints.

3. Project Requirements
1) Build something interesting
2) 3 different budgets
3) Certain time frame (by November 27th 2017)
Objectives
To create a battlebot controlled through an arduino that can move forward/back
and left/right and has an arm that can move up and down, completing the product
in two months (by 27 Nov 2017) at a cost of 45.50 real dollars, 50 UMW dollars at
the ThinkLab, and 25 UMW dollars at the Writing Center.

4. Communications
A. Program Director and Teammates:
a. Text Messaging
b. Email
c. Google Drive (Deliverables, Weekly Updates)
d. Face-to-Face Meetings
B. Stakeholders (ThinkLab, Writing Center, Procurement Officer)
a. Email
b. Face-to-Face
C. Team B and Team D
a. Failure to communicate throughout project.

5. Contract Agreements
● With the Writing Center and ThinkLab
● Negotiation “wins”
○ Charges for use of 3D printer
○ Writing Center Services
● Changes to plans and scope
○ Must be flexible
○ Must make Amendments to Contracts

6. Risk Management Plan

7. Work Breakdown Structure (WBS)
Programming
Battlebot
AssemblyDesign
Prototype
Design 3D Design
Programming
Movement
Programming
Weapon
Casing
Servo
Support
Arm
(Flipper)
3D Printing
Frame
Building
Arm
Design
Bot
Assembly
Case
Design
Microcontroller
Assembly

8. WBS Dictionary

9. Planned Schedule

10. Actual Schedule

11. Budgets

12. Resource Planning
Additional changes:
● Planned to meet weekly with the Writing Center to review progress reports.
● Intended to exchange documents with teams B and D for review.
● Some materials such as Krazy Glue were not required for purchase.
● Extra batteries had to be purchased due to testing issues with servo.

13. Prototype Demonstration

14. The Good, The Bad, and the Ugly
A) Did Well
1. Communication between group members and stakeholders, project manager, and
resource officer.
2. Learning technical skills including: 3D design, 3D printing, and programming.
3. Negotiating skills (price of goods and services).
4. Took a lot of time in the beginning to plan and schedule so we could execute more easily.
A) Not so Well
1. Some milestones were in the wrong order.
2. Although we took time to create a good schedule, we did not stick to it entirely.
3. The week after fall break, we did nothing for this project.
4. Some of our weekly reports were a little late.
5. Remained under budget (had money left over in both accounts).

15. What We Would do Next Time
1. Track actual progress with a separate WBS schedule.
2. Have more regularly scheduled meeting times each week so each member is
involved and updated.
3. Make multiple battlebots so they could battle each other.
4. Utilize the Writing Center more.

16. Top 5 Takeaways
A) Top 5 Takeaways
1. Time management is hard.
2. Plans change, have to be able to adapt.
3. Good communications builds strong working relationships.
4. You have to “go slow to go fast”
5. Dedicated project teams are much more efficient.