Building great teams. Delivering great value.

Agile Hackathon – Roles

Agile Hackathon           Wednesday(May 4) Schedule          Friday(May 6) Schedule           Saturday(May 7) Schedule

Developer Pig

To be a Developer Pig in this event you must have experience in one or more computer programming languages (like C#, PHP, Java, .NET, …) or have some specific software development skill as a DBA, graphic designer, etc.. You will have the responsibility to actually deliver the product specified by the Product Owner using the skills you have chosen for yourself.

YOU WILL NEED TO BRING YOUR OWN LAPTOP FOR THIS EVENT.

Scrum Master

To be a Scrum Master in this event is required at least some experience in Agile Development and Scrum. It will be necessary to manage Task Boards and Burndown Charts,  be able to control conflicts and make sure the Agile Team has the conditions to work smoothly.

YOU WILL NEED TO BRING YOUR OWN LAPTOP FOR THIS EVENT.

“The Scrum Master primary job is to remove impediments to the ability of the team to deliver the sprint goal/deliverables. The ScrumMaster is not the leader of the team (as the team is self-organizing) but acts as a buffer between the team and any distracting influences. The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules. A key part of the ScrumMaster’s role is to protect the team and keep them focused on the tasks in hand”. (From Wikipedia)

Product Owner

To be a Product Owner in this event you need to have a real desire on a specific software project that you would like to see developed in this Agile Hackathon. Passion and knowledge about your software product are requirements to be able to describe and validate User Stories for your Agile Team.

YOU WILL NEED TO BRING YOUR OWN LAPTOP FOR THIS EVENT.

“The Product Owner represents the voice of the customer. He/she ensures that the Scrum Team works with the “right things” from a business perspective. The Product Owner writes customer-centric items (typically user stories), prioritizes them and then places them in the product backlog.” (From Wikipedia)