1. JpMedier workflow
Team’s, sprints, Source Control,
Trunk/Branching

2. The JpMedier Way
•
•
•
•
•
•
4 teams, JPS, Mit Jp, Watches, Jyllands-posten
All use SVN
All use 14 days sprints
All use 1 release at the end of sprint
All use team-city
None has a continuous releasable trunk

3. JPS ( jp services )
• Encapsulation of business logic ( Bordas + own BI
)
• Creditcard handling ( PayEx )
• SSO-ID is primary key, jyllands-posten.dk ask with
SSO-ID / IP and get permissions back
• .net4.0, win2008,mssql2008, iis7.5
• 4-5 developers
• Use Trunk Based Development
• RC is made last day of sprint and disted

4. Mit Jp
• Mit Jp is the relation with Jp’s users, and
creation of new users + webshop
• 4-5 developers, torsdag -> onsdag sprint
• .net 4.5, umbraco 6 Ecommerce4
• Win 2012, msSql 2012, IIS 8
• xWiki for intern doc
• RC is svn tag, trunk locked until dist is done
• RC made last day of sprint, distet the day after

5. Watches
• Watches is niche sites finanswatch.dk .. With a
subscriber model.
• Java, Escenic 5.3, propirioty login system
• IntelliJ12 as IDE, xWiki for doc
• 2-3 deveopers mandag -> fredag
• Use TBD
• RC is svn tag and build from TeamCity
• RC is made last day in sprint
• Dist normaly next wedensday together with jp

6. Jyllands-posten
•
•
•
•
•
•
•
•
Java, Escenic5.3, SSO+JPS login
7 developers + 2 QA in Kiev
2-3 developers + 2 PO’s in Dk
sprint Monday – Friday
2 subteams ( main, project )
Uses Microsoft "Standard Branch Plan” 
Dist wedensday after sprint
Dist is a lot easier on new KIT platform

7. • Every developer merges their issues to trunk,
when tested
• RC verfied on jp-staging
• RC made on Friday, but in real-life many extra
made Monday, Tuesday and even wedensday
• IntelliJ12 as IDE, xWiki for doc
• Can update jp-staging from team-city

8. Git based workflow
• We would love some input

9. SourceControl is useful