• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
MICO Development Infrastructure
 

MICO Development Infrastructure

on

  • 222 views

Development Infrastructure for MICO, Media in Context FP7 Project, presented in the project kick-off meeting, Salzburg , Nov 14, 2013.

Development Infrastructure for MICO, Media in Context FP7 Project, presented in the project kick-off meeting, Salzburg , Nov 14, 2013.

Further details at http://www.mico-project.eu

Statistics

Views

Total Views
222
Views on SlideShare
220
Embed Views
2

Actions

Likes
2
Downloads
1
Comments
0

1 Embed 2

http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    MICO Development Infrastructure MICO Development Infrastructure Presentation Transcript

    • DEVELOPMENT INFRASTRUCTURE Sergio Fernández sergio.fernandez@salzburgresearch.at MICO Kick-Off Meeting Salzburg, 13-14 November 2013
    • working together
    • valuated in $ 22,000 MICO has been granted a Community License
    • Infrastructure smart commits release management + issues.mico-project.eu code.mico-project.eu trigger builds link issues ci.mico-project.eu
    • but... nunchakus does not convert you in a ninja
    • Jira ● ● ● an issue tracker for teams planning and building projects/products But is more, an extensible platform that you can customize In MICO both for: – Project Management – Software Development
    • Issues
    • Workflows
    • Kanban
    • Jira in MICO DoW Work Package Milestone Task Deliverable Jira Project Version Component backlog Epic Deliverable Task Sub-Task Bug all are issues in jira
    • Jira Protocols ● ● Each Work Package (leader) has total freedom for creating its internal components Deliverables are associated with their (Epic) Task according DoW – – ● So all new issues in the project must be linked with their correspondence Epic Task Every Epic Task has total freedom for creating as many issues as needed Assignee resolves an issue when work is complete – Work Package Leader closes (releases) an Epic Task
    • Agile MICO ● Organize sprints with a concrete goal ● Replacing positions by roles – Scrum Master, Product Owner, Developers ● Results-oriented work ● Aligned or not with the DoW milestones
    • Coding ● Code repositories in Bitbucket are synchronized with Jira – – ● Issues can be referenced by citing the issue key in commit messages Some actions allowed via “smart commits” Commits trigger builds in Bamboo
    • GitFlow http://www.atlassian.com/git/workflows#!workflow-gitflow
    • GitFlow http://www.atlassian.com/git/workflows#!workflow-gitflow
    • Deployment
    • hands on!
    • Open to discussion ● Time tracking with Jira? ● Technical documentation ● ... ● Would we need anything else...?
    • Help ● http://quickstart.atlassian.com ● http://confluence.atlassian.com ● http://answers.atlassian.com ● http://university.atlassian.com ● ask ;-)
    • Help
    • gracias DEVELOPMENT INFRASTRUCTURE Sergio Fernández sergio.fernandez@salzburgresearch.at MICO Kick-Off Meeting Salzburg, 13-14 November 2013