sprint.ly @sprintly - Tumblr Blog

New Blog Site!!!

In case our redirect isn't cooperating, please visit us at our new and much prettier blog at https://sprint.ly/blog/. All Sprintly product updates and happenings will be posted to that new site. Cheers!

New Sprintly Feature: Change Item Type

One of our top requested Sprintly features is "how do I change the item type?" Ever file a defect in Sprintly and realize that it should have been a task? Today we’ve shipped this ever useful feature!

Place an item in edit mode via the gear icon, select the new item type and hit Update. In this example, I changed a defect into a task:

You won’t be able to change a Story into another item type at this point. Stories are unique in that they can have sub-items. Tasks, defects and tests cannot have sub-items.

We hope you enjoy this Sprintly product update and always, let us know how we can be of help.

New Sprint.ly Update: Item Detail Modal

Today we released a great new update for quickly viewing an item’s detail and history. We developed a modal for the item detail view. Click on an item’s title and a child window opens up with detailed information for that particular item. You can review, comment and add attachments to tickets without losing your place on the main page. Losing context while reviewing items is a piece of feedback we’ve heard often.

I hope this update helps you use Sprint.ly more efficiently and please keep the feedback coming. We have much more up our (tattooed) sleeves. Stay tuned!

Sprint.ly Welcomes Justin Jackson to the Team!

I'm super-excited to introduce Justin Jackson to everybody today. Justin joined us just this week and will be running Sprint.ly's product marketing. Read on below to learn more about Justin.

Howdy! I'm Justin Jackson and I'm thrilled to be joining the Sprint.ly marketing team.

I've spent the past 6 years working in product management and marketing for a SaaS based web application. In 2012 I started using Sprint.ly to manage my team and it radically improved our development process. Every member of our business could see what was being worked on, and what was finished: for the first time ever, everything was transparent. I've been a huge believer in Sprint.ly ever since.

When I started my podcast Sprint.ly stepped forward to become my first sponsor. As an active member of the product community, I kept seeing Sprint.ly's name pop up as a sponsor for other things as well: Rails Rumble, Django Dash, etc... It's clear that the team is passionate about beautiful products, and the people that make them.

As a product person, Sprint.ly was always one of my favorite products. They seemed to embody everything I liked: amazing design, well though-out user-experience, and commitment to serving all corners of an organization. For me, it's a dream to be working side-by-side with these amazing folks.

New Feature Beta Release: Progress

Tags have always been an important tool in Sprint.ly. Tagging items allows for targeted filtering and is a central feature for organizing and prioritizing sprints and iterations. Today, tags get even a bigger spotlight.

Our team is excited to announce the beta release of a major new Sprint.ly feature: Progress. We designed this report to show burn down and measurable progress over time for each tag in your product.

“Give me a progress report.”

“When will we be done?”

“How much work have we finished so far?”

“Who do we have working on this?”

“What tickets are we working on?”

Progress answers these are the critical project needs and questions.

Progress has been released in beta to a handful of our customers and we will be spending the next few weeks gathering feedback. We’ll incorporate the feedback and release it to the rest of our customers on select plans within a few weeks.

I’m thrilled to share this new feature and as always, I had a great time working with our Sprint.ly design and development team on it. In the words of our founder Joe Stump "Wow. I am excite."

Cheers,

Phuong

P.S. Progress told us when we would be done with this feature and yes, it was right!

6.25.2014 Sprint.ly Product Update

It has been a while since I’ve posted an update on what the Sprint.ly team has been up to. We have been busy looking at our pricing, fixing bugs and last but not least, developing an awesome new feature (more details to come)!

Annual Pricing Plans

We’ve heard a lot of great feedback from everyone about our tiered pricing plans. Today we are happy to announce new annual pricing plans. Sign up for an annual plan and save by getting two months free! Annual Plan FAQs.

NOT DONE Button

In this release, we made a small change to the Reject button for items in the Complete status. The Reject button has been changed to an orange NOT DONE button.

This minor change was made to better delineate a ticket’s reject flow. Tickets from Someday or Backlog can still be rejected via the red Reject button whereas tickets in Complete status can now be sent back to Current with the new Not Done button.

This small UI change is a part of our ongoing effort to add more polish to the Sprint.ly application.

Other Miscellaneous Changes

This release also includes the following changes:

We fixed a defect where the Completed and Accepted sort options were not displayed in their respective Dashboard and Organizer columns.

We fixed an intermittent bug where duplicate notifications appeared after a new item was added.

When an item is unassigned, an entry is now added to the item's history feed as well as to the Activity Feed page:

I hope you enjoyed these updates and as always, we're here to listen to your thoughts and feedback. The team and I can be reached at [email protected].

Cheers,

Phuong

Security Update on CVE-2014-0160 Heartbleed

OpenSSL, the open source cryptographic library reported the Heartbleed vulnerability on April 7, 2014. The vulnerability allows stealing the information protected, under normal conditions, by SSL/TLS encryption.

We have had no evidence that this vulnerability was used against Sprintly but we have taken all necessary precautions to ensure the continued safety of your information.

Actions We Have Taken

Within hours of the official report from OpenSSL, we patched and verified all our servers for CVE-2014-0160.

We use Amazon’s ELB product for load balancing. They patched our region a few hours before we patched our servers.

We have re-issued new SSL certificates to all our servers.

We have rotated all of our SSH, Chef, and AWS API keys throughout our infrastructure.

We have rotated all 3rd party API keys we use to provide services, such as Transloadit (file processing) and Postmark (email).

We have set up our Chef nodes to re-key themselves every 24 hours. We suggest you do the same.

Friday night we flushed all active sessions. This means you will have to log into Sprintly again when you get back to work Monday. Apologies in advance for any inconveniences.

Additional Precautions

You may consider taking these additional precautionary measures on your Sprintly account:

Change your Sprintly password

Reset your Sprintly API key

Both settings may be found in the Profile menu under your Gravatar.

Again, we have had no indication that this vulnerability was used against Sprintly but do feel that it is a good habit to keep your passwords and security keys regularly updated.

If you have any questions or concerns, please feel free to contact us at [email protected].

Sprintly Among Favorite UIs

Sprintly was recently recognized by Software Advice as one of the top five favorite user interfaces in agile project management. Software Advice researched 100s of project management interfaces, selected their top five favorite and in the review called Sprintly's interface "remarkably attractive."

I had a chance to catch up with author Noel Radley to ask her a few questions about herself, how she found Sprintly and what were her primary drivers for selecting Sprintly:

Phuong: Will you give us some background on yourself?

Noel: I’ve been researcher since 2001 (PhD in English), covering topics of technology since 2007. I’ve also taught writing for over a decade at University of Texas at Austin and Santa Clara University. At both campuses, I led research in teaching with technology, including work in Drupal, electronic portfolios, and media production. In February, I joined Software Advice, where my primary research is project management software.

Phuong: How did you find Sprintly?

Noel: It was a rigorous process to select our five favorite softwares. We surveyed 100s of project management interfaces, and we deeply researched about a dozen.

Sprintly showed up as a popular project management interface, and repeatedly we found users commenting on the visual design. As we evaluated the interface, we agreed that it had earned its reputation for compelling design. It really stood out among project management softwares.

Phuong: What were the primary drivers for choosing Sprintly?

Noel: First, we were looking for interfaces that wowed us with beautiful design. Secondly, we were searching for interfaces that helped teams think in critical and productive ways about workflows. We liked Sprintly because it did both. The interface was stunning, while it also provided real insight to project teams.

It’s true there are many interfaces to help track development processes, but we wanted to search for ones that helped developers think in a new way. We feel Sprintly offers unique dashboard views that are conducive in prioritizing, decision-making, and adapting a development workflow.

For example, the Kanban style board is designed in such a way it doesn’t look like your typical card wall, which is refreshing. It also has functionalities your typical card wall may not have, since the cards are more obviously interactive and social than other boards we’d seen.

Phuong: From a UX and UI perspective, do you have any opinions on what a good agile project management tool should provide a team?

Noel: Our article focuses on UI design. To demonstrate great UI, we feel that an agile project management tool would have powerful visual metaphors to help the team conceptualize their work. The tool would be accessible with clearly labelled and categorized features. Finally, in terms of color and composition, the design would make it easy for the team to identify what aspects of the development were the most important at any given moment.

For development teams, the interface should make it easy for teams to view and adapt workflows in real-time.

From surveying these tools, we got a sense that agile project management interfaces are becoming more user-oriented in general. This seemed to indicate an innovative moment for these kinds of software, and the interfaces we selected were leading the way. We can’t wait to see what’s next!

Our UI wouldn't be this incredible without the talents and hard work from our designer Grant Garrett! Read more of Noel's article from Software Advice's website.

#sprintly #QuickLeft #softwareadvice #ui #agile #project management

Pull Request Templates Make Code Review Easier

Last week Justin, our Director of Product Engineering, shared how instituting a simple template makes code review easier for our dev team.

From Justin:

We do a bunch of code reviews at Sprint.ly. One of the things we've done to make that process a little easier is institute a code review template. This template is a free-form list of questions that every person filling out a pull request uses.

Read more from our Quick Left blog and get the PuRTy template from the Chrome Web Store or from GitHub.

#pull request #templates #code review

Help Getting it Right

After shipping out new features and changes to our product, we often get to hear how our customers feel about the changes. There are times where our customers love the changes and then there are times where the changes are just plain disliked.

This was the situation we found ourselves in after we rolled out an update to our Item detail page. We moved the comment & attachment upload box up the page and changed the item’s activity stream into a reverse-chronological order. We had actually made the changes to address customer comments that there was too much scrolling needed on that page.

It turned out that the changes, although well-intentioned for one group of customers, really disrupted another group of customers and their own Sprintly work habits. The number of complaints that came through support, Twitter and our Sprintly Customer Community had the highest velocity we had received to date. So we got together, spec’d out a solution and moved the work up our backlog.

Today we deployed a new option on the Item detail page that allows you to sort the activity stream in chronological or reverse-chronological order:

This new option will help our customers use our system more effectively. Thanks for your feedback and persistence because it has helped us get it right! Now we’re back to work on more improvements, bug fixes and new features.

By the way, we’re hiring designers and full-stack developers in Portland, San Francisco and Boulder. If you're interested in joining the Sprint.ly and Quick Left super awesome teams, Joe and I would love to hear from you!

2.19.2014 Sprintly Product Update

The Feb. 19, 2014's update to Sprintly included a number of key changes.

Change to Item Detail Page

We moved up the comment and attachment upload box on the item detail (permalink) page. It is now located right below the item description:

It was formerly at the end of an item's activity stream, at the bottom of the page. An item's activity stream will now display from newest to oldest. We heard feedback from our users that it took too much scrolling in order to add new comments and attachments.

This is second in a series of updates for the item detail page. We rolled out a big performance boost to this page on February 5th that enabled quicker and more efficient loading. We will continue making additional changes to make this page so it is more user-friendly. We will be incorporating a lot of the feedback we have received from our user base in future releases.

Performance Update - Dashboard

Included in this release is a significant performance patch to the Dashboard that enables quicker page loading. Also, some users were experiencing issues loading new items or items that recently changed state on the Dashboard. We have removed all local caching for the Dashboard to ensure that all item updates are accurately reflected at all times. We will be deploying this same performance update to other Sprintly pages (e.g. the Organizer) in upcoming releases.

Also included in this release is a fix for a display bug where new items would sometimes appear twice on the Dashboard and for a short period of time or until the page is refreshed. This display bug has been resolved in this latest release.

Other Bug Fixes

Other updates include a fix to the email notifications check boxes in Settings. We also added back in a second warning prompt for deleting a product from the Sprintly system.

Phew! Now we're back to working on more performance updates and bug fixes! Please don't hesitate to contact us at [email protected] with any questions or concerns.

#release notes #performance

Raygun Integration

Sprintly is excited to announce yet another awesome integration! Today we feature the Raygun.io integration from our friends at Mindscape. Raygun notifies you of your software's bugs as they happen. With this integration you can attach an error group to a Sprint.ly issue that already exists, or create a new item in Sprintly from an error group. All directly from within Raygun. Read more about the integration here on their blog.

#integrations #raygun

Bugsnag Integration

Sprintly is excited to announce the Bugsnag integration. Bugsnag detects and diagnoses crashes in your applications and now you can set up Bugsnag to automatically create defects within Sprintly. Read more about Bugsnag and the integration on Bugsnag's blog!

#integrations #bugsnag

Flora Worley: My First 4 Months at Sprintly

I’ve been at Sprint.ly for four months, and what better way to celebrate than with a little reflection in the form of a blog post! As those who read my initial “welcome” post know, this is my first official job as a developer. Though it took roughly two years of web-hacking and self-hacking to put myself in the position to get hired somewhere like Sprint.ly, I’m still in shock that I’m actually here now.

Not that I’m resting on my laurels. There’s a lot of hard work involved in transitioning into a new career in a new field. For starters, trying to find my bearings in new piece of software has been like being lost in the garden maze from Alice in Wonderland--just like Alice in the Looking Glass, I sometimes find myself running very fast for a very long time and getting nowhere. There are curious bugs that seem to grow or, if I’m lucky, shrink without much warning. (Just in case you’ve never personally experienced the pleasure of working with Javascript, I’ve come to think of it as the programming equivalent of a fair weather friend: nice when things are neat and simple, but prone to disloyalty.) There’s learning a new culture and the particularities--some might say peculiarities--of our startup: Burrito the Bulldog and a yodeling Affenpinscher playing gatekeepers to the door and the fridge; the subtle pressure to produce hilarious and timely GIFs, a skill that I’ve yet completely and utterly failed to master; the feeling that you’re always running late on a seemingly never ending list of todos.

But for all of my Tweedle-Dum moments, and there have been many, I’ve made some serious headway as a developer since I’ve been here. When I started at Sprint.ly the majority of my experience resided in Python and Django work, and the process of ramping up on Javascript and Backbone has helped me to understand web applications in a whole new way. Our code base is much larger than any project I have previously worked on, and one of the ongoing challenges I face is keeping track of how different parts of our app interact so that I don’t introduce regressions in one part of our code when fixing a bug in another. I’ve poured so much effort into gaining fluency in Mocha, Chai, and Sinon at this point that I now feel that test-writing is one of my strongest skills. And while our team puts a lot of effort into thinking through the architecture of our app as well as our build architecture, I’d like to think that I’m absorbing information around the more meta issues of software development too.

For all this, the highlight of my first few months hasn’t been learning a new language or library; it’s not crystallized in a particular pull request, and has nothing to do with overcoming a particular set of fears (though that’s pretty awesome too). The real highlight of my tenure so far at Sprint.ly has been finding my way into a team of people who care deeply about the product we build, and who care deeply about each other’s success. I’m lucky to work with more seasoned developers who, without having to ask, will take time out to explain technologies that I may not even directly work with, and I never feel like I can’t ask any of my fellow developers a question, or expect to get a thoughtful answer when I’m stuck on something new.

Choosing to be a developer is committing to a lifetime of learning--and there’s a shared understanding here at Sprint.ly, and as we become part of the larger Quick Left team, that we can all help each other to be better craftspeople. If this sounds good to you, take note: we’re hiring!

Announcing the New Voltron in Agile Software Development: Sprint.ly and Quick Left

Those who’ve worked with us at Sprint.ly - as customers, colleagues, and partners - know that we’re committed to our craft. We enjoy pushing the envelope on UI/UX, development methodologies, and technology. At times, this has meant needing to pull in specialists who are working at the very edges of their field to help us deliver. This is how we met Sam Breed and the Quick Left team in Boulder, CO.

Sam is a core contributor to Backbone, which lays at the foundation of our frontend architecture. His contributions to our recent performance refactor have dramatically improved the responsiveness of our application. After completing this project, two things were clear to me:

Sam and the Quick Left team are consummate craftspeople. Delivering quality code and actionable advice took precedence over their bottom line.

I wanted to spend more time working with Sam and the Quick Left team.

Sadly, I couldn’t recruit Sam and he couldn’t recruit me. This mutually sad realization, coupled with Sam’s confession that Quick Left was keen to start building their own products, led me to invite Sam out for beers.

I had an ulterior motive, though, which was to propose that we combine Quick Left’s chocolate with Sprint.ly’s peanut butter. We were building a great product, which Quick Left and their clients used, and Quick Left had an enormous engineering team ready to be aimed at the treasure trove of products swirling through our collective brains.

When our CSO, Matthew Work, first heard the idea he said simply, “That’d work.” Matt’s background at Pivotal Labs running Pivotal Tracker gave him great context to see that this symbiotic relationship had real potential.

Today I’m enormously proud, and exceedingly humbled, to announce that this potential has been realized. Sprint.ly and Quick Left are now one. We will operate offices in San Francisco, Portland, and Boulder. Our mission is to deliver great products - our own and our service customers’ - using the very best technologies and development methodologies available.

Wow. I am excite. Much coding ahead.

Cheers,

Joe

Joe Stump Founder, Sprint.ly @joestump

P.S. You can read more about this awesome news, along with FAQs, on our homepage.

New Feature: Reports

Sprint.ly rolled out a beautiful new collaborative feature today called Reports. Reports is a great way to view items within one product, across all phases and in a grid format.

Features & functions available in Reports:

Pie Chart

Ownership Bar

Full Card / Minimized Card

Sort Columns

Filter by different item criteria

NEW! Filter by Date

Reports is available to existing customers who are on the $14 per person per month subscription plan and for new customers on the Medium and Large tiered pricing plans.

Also included with this Sprint.ly release is an important name change to the existing Items view. We changed it to the Organizer. It is the same great tool but now with a name that is more descriptive of its purpose!

We hope you enjoy it!

Sprint.ly's New Pricing Model

Most companies in the business-to-business SaaS model work on a freemium model or a trial model. We are going to try both.

Gone are the days when you could make a simple software product that serves all customers the same way. We now have to design the whole product and the user experience around it.

These days, a complete product entails marketing funnel, onboarding, discovery, add-ons, and communication. Now we are trying to make a product that offers distinct benefits to different sized teams and people with different roles. Our design challenge is to create a product that can grow with the customer and retain them, while not being overwhelming at the start.

This complexity plays out in our pricing model as well.

We need a pricing model that gets us in the door, charges more as we provide more value to larger teams, and makes enough money to keep us in business!

So we’ve talked to our existing customers, former customers, and prospective customers and have tried to imagine and build a total spectrum product that addresses the problem of “graduation” - the movement of successful growing teams onto more enterprise- focused products.

Today, we’re happy to announce that we have launched a new pricing model. It’s sort of a hybrid between freemium (very small teams are free) and low-cost tiered plans, with high-value add-ons coming soon at most all levels.

We decided that our new pricing model must:

Have a free tier for small teams

Present compelling up-sell opportunities

Match price to value, and not be gimmicky

Encourage the adding of people to teams

Make sense for both makers and managers

Allow existing customers to retain old model if they prefer

We hope you love it. Let us know either way:

twitter: @sprintly / [email protected]

Have some questions? Read some common questions from the Billing sections of our knowledge base.

Trending Blogs

Recently Viewed Blogs

sprint.ly