Courses:Field Robot Summer Course:2012:Team 1

From FroboMind [www.frobomind.org]
Jump to: navigation, search

Sprints

Sprint 1 (August 7th to August 15th)

Sprint planning meeting August 7th

Sprint backlog

1. As a robot owner I want a platform design optimized for robust, accurate and fast driving in row crops under the conditions described here. The platform design must support either trailed or carried implements for eg. crop scouting or weeding.

2. As a robot owner I want a drive train design optimized for robust driving under the conditions described here.

3. As a robot owner I want an energy source capable of delivering enough power for continuous driving in at least 15 minutes.

4. As a robot owner I want one or more fuses protecting the robot electronics.

5. As a robot owner I want a prototype of the designed platform.

6. As a robot owner I want a prototype of the designed drive train.

7. As a robot owner I want a robot computer for the platform supporting WIFI communication for remote monitoring and management.

Sprint review meeting and retrospective August 15th

The sprint has been overall approved.

Points of criticism

  • The budget should have included an estimate of expected future procurements.
  • The stories 5 and 6 from the backlog where not fulfilled but the project owner reasoned that they should not even have been added since they will usually take two weeks to complete
  • There was a problem with the diagram of the electric components and their relationship to each other
  • The fuse and the safety-switch had been mixed up

Sprint 2 (August 15th to August 22th)

Sprint planning meeting August 13th

In the sprint planning meeting we discussed:

  • The importance of correct fusing (50 to 100 mm from battery). Leon has some easy to use fuses and crimp-on fuse holders.
  • How it can be necessary for the team to borrow another robot platform in order to have a quick way to test the electronic and the computer part of the robot. Also it is important for us to use it to gather data. To borrow the platform, contact Kjeld

Sprint backlog

Since story 5 and 6 where not completed, they will need to be done in this second sprint.

After an post-meeting backlog-grooming, the team has decided to aim to fulfill the wishes of the following stories:

05

06

08 As a robot owner I want an in-row positioning system capable of determining the robot position and orientation with respect to the crop rows.

10 As a robot owner I want a headland positioning system capable of detecting ends and beginning of crop rows.


13 As a robot owner I want the robot to be operational on wet soil/grass.

Note that story 09, 11 and 12 has been groomed out for this sprint since the product owner advises that it is unrealistic to be able to do headland navigation and end-row-turning by the end of this sprint.


16/08-12 REMOVED STORY 09 FROM SPRINT 2

Sprint review meeting and retrospective August 22th

Sprint 3 (August 22th to August 29th)

Sprint planning meeting August 22th

Sprint backlog

Sprint review meeting and retrospective August 29th

Product backlog

  1. As a robot owner I want a platform design optimized for robust, accurate and fast driving in row crops under the conditions described here. The platform design must support either trailed or carried implements for eg. crop scouting or weeding.
  2. As a robot owner I want a drive train design optimized for robust driving under the conditions described here.
  3. As a robot owner I want an energy source capable of delivering enough power for continuous driving in at least 15 minutes.
  4. As a robot owner I want one or more fuses protecting the robot electronics.
  5. As a robot owner I want a prototype of the designed platform.
  6. As a robot owner I want a prototype of the designed drive train.
  7. As a robot owner I want a robot computer for the platform supporting WIFI communication for remote monitoring and management.
  8. As a robot owner I want an in-row positioning system capable of determining the robot position and orientation with respect to the crop rows.
  9. As a robot owner I want a navigation system capable of navigating in-row based on the in-row positioning system.
  10. As a robot owner I want a headland positioning system capable of detecting ends and beginning of crop rows.
  11. As a robot owner I want a navigation system capable of making headland turns based on the headland positioning system.
  12. As a robot owner I want a state system capable of switching between in-row and headland navigation, and stop mode based on navigation sensors and user input.
  13. As a robot owner I want the robot to be operational on wet soil/grass.
  14. As a robot owner I want the robot to be operational during sunny and rainy conditions including rapid variations.
  15. As a robot operator I want an emergency stop button which cuts the supply power to all actuators on the robot.
  16. As a robot operator I want a start button which activates autonomous navigation in a row crop field.
  17. As a robot operator I want visual or audio confirmation on the current mode or state of the robot.
  18. As a robot owner I want a carried or trailed implement capable of detecting a marker (marker type freely defined by the development team) placed in a crop row along the path.
  19. As a robot owner I want the robot to perform a creative behavior (freely defined by the development team) to allow participating in the FieldRobotEvent freestyle task.