Setting the business goalsfor a JIRA/Confluenceproject and following upThis is really old hat – S.M.A.R.T.
Why are companies using these systemsin the first place?StrategicgoalsSupportinnovation andcreativitySupportchangeGreatereficiencyUncoverexpertise andrelationsSharingknowledge andpracticeCustomer andpartnerrelationsStrengthencommunityand commongoalsCompanydifferentiationA rewardingand positiveworkplace
Practical roll out of a JIRA/Confluence combinationCollaboration and projectmanagement in an organizationthat is not familiar with theAtlassian toolbox
System features overlap – andsome are missingTask/projectmanagementDocumentationTeamcollaboration• Make clear choices - and stick to them• Use macros and blueprints• Get plugins for special needs• Consider external systemsInvoicingEmailmarketingWireframingExternalhelp deskTime trackingProgram/portfoliomanagement
Important implementationstrategy questions• Are the users in your JIRA andConfluence systems the same?• Are you matching Projects and Spacesstructurewise?• Are you migrating from other systems?• Are you using external system such asMailchimp, Zendesk or SharePoint?• Will the plugins you are betting on stayupdated?
Think of your target groups andtheir needs• What data do you need to create?• Weekly performance reports viaemail?• Web based assignment info?• Word file or Excel sheet formeetings?
Stale platform•All tech and no comms•Wrong platform•Long wait for Big bang•Culture trumps strategy•No content maintenanceCulture•The Man’s tool•Distraction•Too funky•Just more hassleProject issues•Uneven rollout•Losing pace•Obstruction•Frontloaded budgetSignificantimplementationrisks
Checklist for successfulimplementation Ignore fashion when choosingplatform It is a change project, not an ITproject Define project goals clearly andfollow up Avoid Big Bang rollouts One message once is neverenough Recruit opinion leaders Make it easy to participate Avoid fancy acronyms or names Avoid empty spaces orcommunities Use macros, blueprints andplugins to create great solutions Research existingprocess, channels, terminologyand org Get real people and projectsinto the platform early on Make it social (pictures, links) Integrate – don’t create awalled garden – rememberlegacy data Avoid too many customworkflows, issue types,priorities and fields Get enough licenses Use the system in the process Make sure to create local value Be generous, not strict Supply solutions, not demands Management must participate Involve your IT department