If you are tracking progress in actual hours/days in sprints, ScrumPad offers the most insightful time tracking tools. You can see time summary by developers in a sprint. You can then drill down how each developer spent his or her time on different stories/bugs down to task level each day. We call it developer time analysis. Or you can flip the lens and look at time spent by stories/bugs and drill down to time spent on tasks by developers every day. We call it story time analysis.

Each team member has his/her own timesheet only showing stories/bugs and associated tasks assigned to him/her in a sprint. This makes it easy to track individual work.

See a summary of important activities as they occur on a given day in one place. Filter events by event types associated with story, bug, task, impediments, messages, and comments. Browse daily digests by day. Never have to worry about missing any event that is important to you. You are always up-to-date.

URL:

http://www.scrumpad.com/api/projects/:project_name/stories/:story_id/testcases.format

Formats:

xml

HTTP Method(s):

POST

Authentication:

Http basic authentication is required. Use your ScrumPad user name and password for the authentication.

Usage examples:
curl -X POST -H "Content-type:application/xml;character-set:utf-8" -u user:password --data-ascii @request.xml https://www.scrumpad.com/api/projects/:project_name/stories/:story_id/testcases.format

Parameters:

project_name: Required. The name of the project, should be unique for the ScrumPad account. Must not contain any special characters.

Request Xml:

<?xml version="1.0" encoding="UTF-8"?>
<test_case>
   <!-- this is optional, but can be used to cross link a testcase between ScrumPad and external testing tool-->
   <ext_ref_id>1</ext_ref_id>
   <story_id>29</story_id>
   <text>Test case from api</text>
</test_case>

Response:

Returns newly created testcase with the unique id.
XML example:

<?xml version="1.0" encoding="UTF-8"?>
<test_case>
  <id>1</id>
   <ext_ref_id>1</ext_ref_id>
   <story_id>29</story_id>
   <text>Test case from api</text>
</test_case>

URL:

http://www.scrumpad.com/api/projects/:project_name/stories/:story_id/update_test_status.format

Formats:

xml

HTTP Method(s):

PUT

Authentication:

Http basic authentication is required. Use your ScrumPad user name and password for the authentication.

Usage examples:
curl -X PUT -H "Content-type:application/xml;character-set:utf-8" -u user:password --data-ascii @request.xml https://www.scrumpad.com/api/projects/:project_name/stories/:story_id/testcases.format

Parameters:

project_name: Required. The name of the project, should be unique for the ScrumPad account. Must not contain any special characters.

build: Required. Name of the build (version of code) this testcase was run against.

Request Xml:

<?xml version="1.0" encoding="UTF-8"?>
<test_result>
   <id>1</id> <!-- testcase id, unique within the story or bug -->
   <story_id>15</story_id> <!-- story id, unique within the project -->
   <sprint>Sprint#3</sprint>
   <build>Build 1</build> <!-- it is a required field -->
   <status>passed</status>
   <test_date>09-09-2011</test_date>
   <tester>srayhan</tester> <!-- ScrumPad user name of the tester -->
</test_result>

Response(return values):
XML example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
    <!-- success or failure message. If the HTTP return code not 200, then it is an error message -->
</result>

URL:

http://www.scrumpad.com/projects/:project_id/sprints.format

Formats:
xml

HTTP Method(s):
GET

Authentication:
Http basic authentication is required. Use your ScrumPad user name and password for the authentication.

Parameters:
project_id: Required. The id of your project

Usage examples:
curl -u user:password http://www.scrumpad.com/projects/123/sprints.xml

Response(return values):
XML example:

<?xml version="1.0" encoding="UTF-8"?>
<sprints>
  <sprint>
    <id>12</id>
    <description>Define architecture and setup environment</description>
    <name>Sprint#11</name>
    <project-id>158</project-id>
    <release-id>148</release-id>
    <is_completed>false</is_completed>
    <start-date>2008-07-10</start-date>
    <end-date>2008-07-24</end-date>
  </sprint>
  <sprint>
    <id>8</id>
    <description>UI implementation</description>
    <name>Sprint#1</name>
    <project-id>158</project-id>
    <release-id>148</release-id>
    <is_completed>true</is_completed>
    <start-date>2008-06-09</start-date>
    <end-date>2008-06-23</end-date>
    <created-at>2008-01-01</created-at>
  </sprint>
</sprints>

Syed has 15 years of IT industry experience designing multi-faceted IT solutions for Fortune 500 companies. He has been practicing Agile/Scrum since 2004. He is a an Agile coach, and a Certified Scrum Practitioner (CSP), and is a member of the Scrum Alliance. He has been using Agile/Scrum in delivering outsourced projects at Code71.  He co-authored Enterprise Java with UML (pub. Wiley and Sons) and have presented on Agile/Scrum related topics at various conferences.

Syed is a student of “Lean Startup” and applying “Lean Startup” principles in building ScrumPad business. When not working on ScrumPad, he plays poker. He dreams of playing poker professionally and win WSOP title someday.

Syed holds an MBA from the University of North Carolina, Kenan-Flagler Business School, as well as, an MS in Computer Engineering from the University of Central Florida and an undergraduate degree from BUET (Bangladesh University of Engineering Technology) in Electrical & Electronic Engineering. You can follow him on twitter @srayhan and read his blog. Nimat Haque
Co-founder

In a leadership role for the past eight years with Capital One, Nimat has demonstrated her ability to build and lead teams to successful outcomes. With interests in the people aspect of software development, she brings a passion for building teams that are self-managing and empowered to drive results through innovation.

Nimat holds an MBA from the University of North Carolina, Kenan-Flagler Business School, as well as, an MS in Computer Engineering from the University of Central Florida and an undergraduate degree from BUET (Bangladesh University of Engineering Technology) in Electrical & Electronic Engineering. Additionally, Nimat is currently serving on the board of CASA. Previously she served on the board of the Commonwealth of Virginia Girl Scouts Association for 2 years. ]]> http://scrumpad.wpengine.com/about/core-team/feed 1 http://scrumpad.wpengine.com/api/get-information-of-logged-in-user http://scrumpad.wpengine.com/api/get-information-of-logged-in-user#comments Mon, 28 Jun 2010 09:44:41 +0000 admin http://www.scrumpad.com/?p=348 Returns information about the logged in user.

URL:
http://www.scrumpad.com/users/current.format

Formats:
xml

HTTP Method(s):
GET

Authentication:
Http basic authentication is required. Use your ScrumPad user name and password for the authentication.

Parameters:
Not required.

Usage examples:
curl -u user:password http://www.scrumpad.com/users/current.xml

Response(return values):
XML example:

<?xml version="1.0" encoding="UTF-8"?>

Like many, we started with good old Excel spreadsheet and emails for keeping track of our stories/feature requests, bugs, iterations (sprints), burndown charts, and times. However, in remote delivery environment, it soon became a major headache. We looked for a suitable agile project management and collaboration tool at a reasonable price. We selected “Version One” in 2006. Although it provided a lot of flexibility, but it took us a good couple months to learn how to use it. When we asked our clients to start using it, they also found it difficult to learn. So, we looked for another tool that is simple to use. And we found one called “Basecamp.” I am sure many of you are using it. We all including our clients picked up the tool in no time. Life became a little easier. However, since it was not designed for Scrum, we had to improvise how to adapt it for Scrum. One glaring issue though still remained with Basecamp. Its time tracking and estimation mechanism was not suitable for Scrum and so we had to continue to use Version One.  Also using two tools for managing projects became a hassle. So, we finally decided to build something that will make our life simple for forever. ScrumPad was born.

We first tried to extend Basecamp to add missing features. Soon we realized that there is a natural impedance mismatch between Basecamp project management model and Agile / Scrum project management model.  Also having project data live across two independent services and legal & operational issues that could potentially arise from that, the benefit of extending Basecamp does not make it worth while to take on the risks for both our clients and us.  So, we discarded the work of extending Basecamp and restarted from scratch. The rest is history.

Yes, that’s right! We want to make using project management tool “Fun,” period. We feel that all project management tools  in the market are boring. That is why we always see a debate about “to use or not use” a tool when it comes to project management, specially Agile. If you think about it, this debate is oxymoron in some ways, since we are in the business of making software tools to help others do their job better. Then why we are against using a tool for ourselves. The answer lies in the fact that the project management tools as we know them are very cut and dry.  We dread in the thoughts of using “yet another one.”

Fun does not mean not useful. Of course, ScrumPad will provide all things (e.g., requirements management, bug tracking, test management,  estimation, time tracking, planning, etc. etc.) that other tools provide. But, we will weave them into “a social fabric” so that it is fun doing so. We all know working on projects, specially on software projects is highly social. There are dramas. There are triumphs. There are failures.  Project management tool should embrace this social aspect of project. It should not be just bunch of words, numbers, and spreadheets.

You might be thinking to yourself  by now, “This sounds great, but very philosophical. What does it mean for me?“

You are probably right. Did we figure this all out yet? No.  But we know with your help and feedback, we all will get there. We are iterating, and iterating fast. Fogs are clearing, layer by layer. Here are a few specific goals that will help this vision come true,

We want to make ScrumPad fun to use everyday for our users like they do Facebook or Twitter,

We want ScrumPad to be pragmatic, and not prescriptive or limiting, last but not least

We want ScrumPad to be a platform nurturing “a project eco-system,” not just a mere tool

We are on a journey to revolutionize how we see project management today. Do you want to join us in this journey? Please signup and start using it today and take part in a history in the making. Slowly, but surely we will make good on our vision with your active support. And YOU will at the front and center behind that success!