Who are we?

A company that brings start-ups and other Agile software development projects into life, following Agile principles rigorously,
trying to follow Scrum framework as much as we can, using JIRA and its JIRA Agile plugin.

At one point we realized that we just needed additional tools (such as Excel) to make our initial planning process smoother,
so we made a plugin for ourselves to replace them and now we are bringing it to you to see if you like it as much as we do.

Is Plangle for you?

Well, we recommend it only for those who

• use JIRA Agile (ex-Greenhopper) and its new Scrum boards
• but miss (mainly for initial planning)
  • an Excel-like hierarchical view of your Backlog
  • a lightning fast editor
  • simple but anti-book features like
    • making Story estimations equal to the sum of the estimation of its subtasks
    • creating sub-tasks per activities quickly (like Frontend, Backend, QA, etc.)... we call them Quick Subtasks, aren't we creative?
  • the ability to answer to "annoying" questions such as "What will be ready by November 30 guys?"
• believe in the Agile principles and try to follow the recommendations of the Scrum framework
  • even if they are not always sure about how to apply them in real life correctly
• need a tool which is open to support any reasonable real-life-compatibility patches to Scrum

So it does NOT matter whether you are a chicken or a pig...

• • Scrum Master
  • Product Owner
  • Team Member
  • Project Manager (yes, we know that it is not a Scrum role, but still an existing position in companies of real life)
     
  • or just any other guy in your organization who has to deal with JIRA Agile boards

...if you like our features, don't hesitate to use them!

And if you don't... it makes us sad, so help the Earth be a happier place and let us know why you don't like it.

Expectation management

This section is created to prevent you from feeling disappointed after giving our plugin a try,
therefore keeping our Marketplace rating reasonably high.

What should you expect from Plangle?

• A super-fast hierarchical editor which is a great addition to the "Plan" view of JIRA Agile
  • many features are coming on their way (like Sprint filter, Quick filter support, etc.)
    
    
• Plain answers with easy-to-follow explanations to difficult questions during your project... but focusing on initial planning (so far)
  
  • What would be the ideal team structure for the project? (Frontend, Backend, QA people, Designers, etc..)
  • How fast can we be considering our past?
  • When will the whole project be ready?
  • How much will the whole project cost?
  • How much will each feature cost? (well, approximately)
  • What will be ready until... set date?
     
• Full integration with JIRA Agile concepts and board configuration
  
  
• A team which is ready to support how you implement Scrum and Agile, just let us know what you need!

What should you NOT expect from Plangle?

• To be a replacement of JIRA Agile or Tempo Planner
  • JIRA Agile is a great tool on its own (we use it every day and are quite happy with it)
  • Tempo Planner is also great stuff for release/iteration/capacity planning, we are not in that business (yet)
  • Plangle is not for replacing any of these but it helps you to simplify your calculations/planning in Excel and TXT files

• To answer questions
  • based on
    • non-Agile plans like a Gantt-chart, specifying what Eric Cartman will do instead working on your project at 9:15 next year, October 23th (we just don't believe in these kind of plans)
    • a project manager's expectation on how long the "Login with client certificate" story should take (we already did a Facebook login last time in 4 hours, did not we??)
      • we believe in measured results as soon as it is there (during the project)
      • and team estimation/commitment (before you start the project)
  • without any reasonable data backing it
    • you can't guess who will do a feature two month ahead, we don't have the Eyes Of Nostradamus (if you do, go ahead, we won't prevent you from doing that)
      
      
• To follow what The Book (you've just read) says rigorously
  • we believe in Agile and not a single book
  • we try to follow all the best practices where "best" means that our customers and/or ourselves found them useful in practice (probably written in some of the books or course)