Land the Tech Job You Love


Product Details

$23.95  $22.27
Pragmatic Bookshelf
Publish Date
6.02 X 8.92 X 0.52 inches | 0.75 pounds

Earn by promoting books

Earn money by sharing your favorite books through our Affiliate program.

Become an affiliate

About the Author

Andy Lester started with computers early by keypunching letters to Grandma on IBM 029 punchcards. Now into his third decade of professional software development, he's the QA & Release Manager for Socialtext. Andy is also in charge of PR for The Perl Foundation and maintains over 25 modules on CPAN. Andy's two latest book projects are Mac OS X Tiger In A Nutshell from O'Reilly, and Pro Perl Debugging from Apress. 04.19.2013 Platform Retrospective Attendees: Vered, Sarah, Jeff, Marcel, Matthew, Laura, Adam Start working together on Tasks within a Story for more successful completed stories Keeps people more engaged in meetings since everyone is part of story Helps keep team focus Continue having shorter review meetings by getting early acceptance Keep to 15 minute Stand Up Meetings Start discussing issues prior to meetings to keep moving forward Stop stressing to get meeting over - feel good to discuss what is needed Work outside of Sprint prioritization Work with Manager outside of Team to align work and time spent Start having notes ready for last/next 24 / blocks to keep reporting quick Start calling 'further discussion' meetings if Open Floor is going long If Open Floor topic going long, invoke 5 minute rule to move to another time Ask if everyone is good to stay on or need a follow on Start - G2 reach out to anyone needing to be on Stand Up Start, more Product Owner buy in for the details To help avoid missed details where no one person owns the full process Product review of done-done - Demo Watch for changes to environment requiring a retesting Out of Cycle Release - CCD for all to view, exposure of release to QA Other options to expose release/changes to code/environments Poss: build release manager Avoid too much "process" Stakeholder - Product Owner When differences occur, how best to communicate Acceptance Criteria is contract with Product Owners 04.05.2013 Platform Retrospective Attendees: Marcel, Adam, Jeff, Sarah, Rachel Do not add User Stories in middle of Sprint A lot of stories rolled over Multi teams are requesting time of same resources Both people and environments Time put into tasks to handle issues of prev sprint deliverables Tasks can be added as needed - but wont show in planning Stories small enough to be end: end deliver/test Add hours in testing stories to have hours to fix failures Test plans cover full expectations of the Business acceptors Doable Acceptance Criteria Shorter, more focused meetings Full attention in meetings Avoid being pulled into areas not covered by team/sprint Get acceptance prior to Review meeting where possible Assures story has been completed