Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Pivotal Tracker Control Matrix

Pivotal Tracker Control Matrix

Ratings: (0)|Views: 7,513|Likes:
Published by Peter Saddington

More info:

Published by: Peter Saddington on Dec 23, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Control – SDLC – Pivotal – Request Tracker Matrix
ControlSDLCPivotal (& Request Tracker)
Change RequirementsRequestor / Stakeholdercreates a StoryEnters into Pivotal, where stored in “IceBoxbucket in Pivotal.Change RequirementsFurther Story ElaborationWhile in IceBoxUser Acceptance TestingRequestor / Stakeholderdefines Story Test PlansAcceptance Criteria (test plans) is included inStory when it is entered into Pivotal.Change RequirementsEstimateWhile in Ice Box sometimesChange RequirementsFeature Prioritization occursduring Iteration or ReleasePlanning and/or ScheduleElaboration and EstimationMeetingOnce meeting occurs, Stories move to “Backlog”bucket in Pivotal, which is the official approval of the Change Request to be worked.Backlog reflects current prioritization and iscontrolled by the business.DevelopmentDeveloper hits Startwhich means work hasbegun.Story is moved to “Current” bucket in Pivotal.Once development is complete – developer hits“Finish” button, which means it is ready forStakeholder review/testing.Email is automatically sent to Requestorindicating ready to test.Remains in “Current” bucket in Pivotal, with anindication that it is “Delivered” meaning ready fortesting by Stakeholder.User Acceptance TestingStakeholder / Requestortests changes usually in Devenvironment, sometimes in QAenvironment.If “Approved,” Stakeholder/Requestor hits“Approve” button, which is indication that it is readyfor QA team to test.If “Reject” button is hit, the Story goes back intoa Restart state for developer to restart. See aboveunder Development.Release Markers here or sooner to indicate whichStories are included in a Release.1
Control – SDLC – Pivotal – Request Tracker Matrix
User Acceptance TestingQA conducts testing – unit usually in DevRegression and Integritytesting of entire Release in QA.Standard Critical Pathdocument for that particularproduct is used as the QA TestPlan.If defects found, they aresent back to developer to befixed.When testing is completed,they sign off.Remains in “Current” bucket through testing.If bugs are found, “Defect” Story entered intoPivotal, then Story is “Started,” then put back intothe Release (or left in the Backlog if taken of Release. When testing completed, QA hits “Finish”button which indicates their testing sign-off for theRelease.Implementation intoProductionOnce testing is completed,Deployment by Infrastructure Team can occur.QA creates a staging ticket in Request Tracker(not Pivotal) to stage the release into production.Once Release is migrated to production, QA willperform Critical Path Testing and update stagingticket with test results. Infrastructure will thencloses ticket and email is sent to QA requestor andappropriate management team indicating releasehas been migrated.CommunicationAppropriate project managersends a communication tobusiness owners and users(where appropriate) withhighlights of what was includedin the release.Action Item: This email needs to be retained.2

Activity (5)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
poweredgeus liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->