AgilePress uses the familiar WordPress admin screens for the bulk of its setup.  Although most AgilePress functions can be done from the boards themselves, the Admin post screens are where a new AgilePress administrator should start.

Upon installing and activating AgilePress, the left-hand WordPress admin menu will contain an “AgilePress” entry with the following options:

  • All Products
  • All Sprints
  • All Tasks
  • All Stories
  • Get Help

(Chances are, you’ve found that last one already since you’re here!)

All Products

This shows a list of the products that you’ve defined to AgilePress.  A product is the central aspect of AgilePress; it’s what you’re working on.  This is often a software product, but it doesn’t have to be; it could be anything from your house (maybe you’re remodeling or even buying a house), a project (“produce documentation for our company’s travel procedures”) or even you (the Kanban board is great for personal improvement!)

Adding a new product is the first thing you should do after installing and activating AgilePress:

AgilePress uses the “excerpt” field for the body of notes.  The additional fields – Current Version, Target Version, and In-Progress Version Status – are purely informational.

AgilePress is very lenient; you can add tasks, stories, and sprints without a product.  You can’t display a board without a product, though.

All Sprints

The “All Sprints” list adds a couple of noteworthy features.  First, as you can see, the associated product (assuming there is one) is listed.  Notice that the “Filter” section at the top of the list adds Products to the possible options; this allows you to narrow by a product in addition to dates, category, etc.  This is useful in the event that you have a large number of sprints.

The other feature is the shortcode display; this is what you would copy to a page in order to get the Sprint Board to display.

Start and End Dates are informational, as is Sprint Status; these help you and your team know when a planned sprint will begin.

The Backlog Target field, however, is functional.  On the backlog board, the third column is “Send to Sprint” and the sprint labeled as “Backlog Target” is where stories moved to the “Send to Sprint” will go.  If you have more than one sprint marked as a backlog target, AgilePress will take the first one it finds.  (If you do not have any sprint marked as a target, AgilePress will still create a task from your story; it will be listed when you go to the “All Tasks” menu option but will not appear on a board until you give that task a sprint.)

All Tasks

(in progress)

All Stories

(in progress)


Copyright 2017-2019, KMD Enterprises, LLC