Intro to Jira

Hi Marketing Team,

As many of you have heard by now we are transitioning to Jira in the coming weeks. Jira will replace fogbugz as our project management tool here in marketing. As we transition I will keep you all updated on which teams will be transition when so you can start diving in and utilizing Jira.

You will find login instructions below and here is a link to the user guide.

Please take the time to read the below information regarding the transition.

To give you a little more information and to answer a few questions that have come up in the last couple of weeks.

  1. Is Marketing the only department switching to Jira? We as a company are transitioning to using Jira. Eventually fogbugz will be replaced all together and we will no longer be using it.
  2. How will this effect working with other departments? As we have transitioned to more of a line of business model here at Faithlife there will be more opportunities to work on projects with other departments. Jira will be a great tool in which we can work on cross department projects with other teams.
  3. Are we required to use Jira? What if we like what we are doing? As much as possible we ask that each team and individual use Jira for all of their projects and tasks.
    1. Why, you might ask? A few great benefits of Jira:

i.     Everything for your project is in one place. You will no longer have to add everything to the wiki, asana, google docs. (This doesn’t mean that we won’t use these tools anymore, but the amount of duplication and where you need to add information will become less repetitive.)

ii.     Management will be able to pull reports from Jira, decreasing the number of reports you will need to turn in or fill out on a weekly basis, giving you more time to work on your projects.

iii.     Time Tracking will become a lot easier!! We will be switching to a monthly time tracking system with time tracking by project for LARGE projects.

iv.     Jira is more user friendly than fogbugz.

How does this affect you now?

  1. You will want to set aside sometime over the next few weeks to get familiar with Jira, go through the user manual and attend the training that you are scheduled for.
  2. Any projects you have in fogbugz will be migrated over to Jira in the next 6 weeks at which point you will be working solely out of Jira.
  3. You will need to work in both Fogbugz and Jira until all teams has been transitioned. As much as possible we ask that once a team is transitioned you enter any new requests in Jira rather than fogbugz.
  4. Any projects that are not in Jira will need to be put in manually by you.
  5. As teams transition over you will need to start submitting your request in Jira (even if your team is still working in fogbugz and hasn’t been transitioned over).

A few terms to familiarize yourself with:

  1. Issue: An issue is equivalent to a parent case in fogbugz
  2. Project: A project is equivalent to a project in fogbugz (For example our current projects in fogbugz are: Marketing Projects: Logos, Marketing Projects: Ecommerce, Marketing Technology Team, etc.)
  3. Task or Sub-Task: A task or sub-task are equivalent to a child case in fogbugz

 

How to Login:

You all currently should have access to Jira. If you are unable to login please let me know.

To login, follow these instructions:

Go here:  https://faithlife.atlassian.net/login (you may want to bookmark this)

  1. Your username is everything in front of the @ on your faithlife email address.
  2. If you don’t have a password, click unable to access your account, and you will be prompted to create a password.

As you start exploring the tool, know that we are still making changes and these changes will continue to take place over the next 6 weeks as we get everyone transitioned over. Please be patient and ask lots of questions. If you aren’t sure how to do something connect with your team lead first, if they don’t know the answer then feel free to reach out to me.

Please let me know if there are any questions or concerns.

Thanks!

 

Kirsten

KPCB Internet Trends 2013

“The latest edition of the annual Internet Trends report finds continued robust online growth. There are now 2.4 billion Internet users around the world, and the total continues to grow apace. Mobile usage is expanding rapidly, while the mobile advertising opportunity remains largely untapped. The report reviews the shifting online landscape, which has become more social and content rich, with expanded use of photos, video and audio. Looking ahead, the report finds early signs of growth for wearable computing devices, like glasses, connected wrist bands and watches – and the emergence of connected cars, drones and other new platforms.”

Primer: Touch First Thinking for Web

One of the big areas I would like for us to touch on as a department is the idea of pushing our design and web content into the touch first mentality. The reason is simple. Our audience is shifting to mobile for both viewing and purchasing on the web. Specifically tablets.

For the period of April 6 through May 6 this year and last year:

  • Biblia.com mobile traffic increased nearly 250% (90K visitors to 318K)
  • Logos.com mobile traffic increased 25% (82K vistors to 102K visitors)
  • Logos.com revenue from mobile traffic increased 83% (from $54K to $99K)

We have also seen a year over year increase in mobile revenue on Logos.com since 2009. The below chart shows a comparison of revenue on Logos.com from desktop and mobile traffic. The big take away from the chart is the 100% increase in mobile traffic and 93% increase in mobile revenue in the past twelve months. That segment of our visitor base to Logos.com is growing more rapidly than our desktop user rate and his exceeded $1M in the past twelve months.

Logos.com mobile revenue

Logos.com mobile revenue May 2012 – May 2013

To sum up we need to move to think touch first for web design.

Prefer interaction paradigms that are natural for touch (such as swipe for slide decks and carousels).
Minimize the use of mouse interaction paradigms (such as hover states).
Emphasize design and implementation to fit well with landscape view for iPad (it is a reasonable standard).

Finally I wanted to post a conversation between Shiloh Hubbard and I from earlier (which prompted this post):

  • Shiloh: [in regards to “touch”] the idea is quite literally have no hover states? or only because it adds a step for mobile devices users?
  • Nathan: http://globalmoxie.com/blog/desktop-touch-design.shtml. That is a great article. I will send it around.
  • Shiloh: thanks, i’ll give it a read
  • Nathan: Hover states are only one part of the equation. Currently, most places design with mouse navigation in mind. Embedded links, lots of text in drop downs, etc. When you go to a website and you have layered navigation, on a desktop you hover then go to what you want. On a tablet, you click to get the drop down, then you click to get what you want.
  • Shiloh: Right.
  • Nathan: So everywhere we can we want to rethink the paradigm; if hover is necessary and advantages, how then do we make it seamless for a touch interface to interact with that? So it is not an abolition of hover, just a re-thinking of how often and where we use it.
  • Shiloh: Gotcha.