To be a Developer Pig in this event you must have experience in one or more computer programming languages (like C#, PHP, Java, .NET, Ruby, ...) 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. Also, at the first night of the event, the Developers are going to play the Testers role. YOU WILL NEED TO BRING YOUR OWN LAPTOP FOR THIS EVENT.

The System Architect, in this event, will be responsible to specify the environment that is going to be used by the Development Team, give architecture support for the Team during the Sprints and have the application deployed ready for the Demo meetings. YOU WILL NEED TO BRING YOUR OWN LAPTOP FOR THIS EVENT. "The main responsibilities of a software architect include: Limiting the choices available during development by choosing a standard way of pursuing application development creating, defining, or choosing an application framework for the application. Recognizing potential reuse in the organization or in the application by Observing and understanding the broader system environment. Creating the component design. Having knowledge of other applications in the organization. Software architects can also: Subdivide a complex application, during the design phase, into smaller, more manageable pieces Grasp the functions of each component within the application. Understand the interactions and dependencies among components. Communicate these concepts to developers In order to perform these responsibilities effectively, software architects often use Unified Modeling Language and OOP." "Design: The architect makes high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms, so as to advance business goals rather than to place arbitrary restrictions on the choices of developers . Note that software architects rarely deal with the physical architecture of the hardware environment, confining themselves to the design methodology of the code. Communication: Architects also have to communicate effectively, not only to understand the business needs, but also to advance their own architectural vision. They can do so verbally, in writing, and through various software architectural models that specialize in communicating architecture." (From Wikipedia)

To be a Scrum Master in this event is required at least some experience in Agile Development and Scrum. Will be necessary to manage Task Boards and Burndown Charts, be able to control conflits 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)

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)