Software Releases

Thread is closed for posting
2 posts, 0 answers
  1. John
    John avatar
    19 posts
    Member since:
    Dec 2011

    Posted 28 Jan 2012 Link to this post

    As our develoment team starts to investigate a more agile methodology I have a couple of question regarding how to transition from our current methodology to Team Pulse.   

    Here is our current workflow:

    Project XYZ
                  Release 1.0  (3) composed of  3 iterations each 
                            Iteration 1.0.1  Send to QA
                            Iteration 1.0.2  Send to QA
                            Interation 1.0.3 Send to QA

                  Release to Customers

                  Start work on Release 1.1 composed of 2 iteraction
    How does this translate into Team Pulse
  2. Kamen Ivanov
    Kamen Ivanov avatar
    80 posts

    Posted 30 Jan 2012 Link to this post

    Hi John,

     For each created project there is one default iteration named "Project" this is the timeline for your project. It's start date is the date when the project is created and the end date is the end date of the last iteration. It cannot be renamed or deleted and is parent for all iterations in your project.
      The iterations are hierarchy structured so you can easily maintain and accomplish the desired hierarchy. I've attached a screenshot showing how your example will look like in TeamPulse.

    Kamen Ivanov
    the Telerik team
    New TeamPulse release is here!
    Want to know what’s New and how TeamPulse could help you better tight with your clients?
    Reserve a seat for the TeamPulse R3 Webinar today!
Back to Top