View Single Post
  #11   Spotlight this post!  
Unread 29-12-2015, 20:19
GeeTwo's Avatar
GeeTwo GeeTwo is offline
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,605
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
Re: Advice For Agile/Scrum Robot Development

Trying to put together what everyone is saying, both here and on the other recently-necro'd scrum thread:

Treat scrum (or any other development management process) as you would treat a great drive train or manipulator design or reveal video you find on Chief Delphi:
  • Consider what problems you have that it might solve.
  • Consider whether you have the resources (time, talent, training, treasury) to accomplish it.
  • Consider whether there are pieces of it that you can adopt or adapt into your development.
  • You may decide to use it all, use none of it, or use a few bits and pieces.
  • After you give it a try, figure out what worked and what didn't. Iterate and make it better!
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.
Reply With Quote