RE: CSM - Chennai
Amol Patki
First CSM group that was trained under you has formed
A google group with the name: Chennai Scrum
Group owner : pma....@gmail.com
Regards,
Amol Patki, MBA,PMP,CSM
Management Consultant
Mobile : 91-9789851120
-----Original Message-----
From: Kiran Thakkar [mailto:tkir...@gmail.com]
Sent: 09 September 2011 14:26
To: Amol Patki
Subject: Re: CSM - Chennai
Hi Amol, What is the group name? I want to join the group.
Thanks,
Kiran
On Jul 22, 2011, at 1:16 PM, Amol Patki wrote:
> Hi All,
>
> Thanks Antony for creating Google group and the invite to join the group.
> Hope next discussion will start over there.
>
>
>
> Experience shared by Balaji was
>
> Currently they have separate sprint for development and QA, If there is a
> sprint that has Both Dev and QA activity combined, how we manage the
> Developer's time while QA is in progress.?
>
> Problem identified : Tasks Dependency, Resource utilization
>
> My take on this:
>
> There should not have separate sprints for completing minimum marketable
> features (MMF’s), i.e. ready to ship software to get full benefits of
agile.
>
>
>
> Team does planning at 3 levels Daily Stand up, Iteration, Release ( Which
> MMF’s will be shipped ? Collection of high priority Epic/User stories
> (Product Backlog ) ->Tasks (Sprint Planning) - >
>
> Daily Stand up 3 Q’s (daily instantaneous replan).Resource utilization
> problem may be occurring as Dev/ Tester are dedicated to the team
>
>
>
> Release Planning : No problem
>
> Sprint planning
>
> US1-> Develop 14Hrs- Unit Test 2Hrs (Incremental testing)- > (Hand over
to
> Tester)-> Go to next feature
>
> -> Testing criteria->Understand (3Hrs) -Prepare Test plan(1Hrs)-Test
> data preparation(2Hrs) -> Prepare Test cases(8)-> Receive testable code ->
> start work->test complete(Incremental testing)
>
> If there is any slippage at any time , daily stand up gives you
opportunity
> to replan.(Iteration)
>
>
>
> If tasks are put up on scrum/ kanban board, tester will act on the task
only
> it is place under “done “ column, it’s pull system driven by Lean as story
> is been developed as a value to customer pulled during development cycle
by
> the next process and cycle will be slowed down and will be work @ the
speed
> of slowest mover (Constraint) during value chain. (SM area!!!)
>
> è Resource expertise
>
> è Task planning
>
> è Impediment mgmt (Issue resolutions)
>
> è Other dependencies
>
> è Org Structure
>
> è Work locations
>
> è Etc.
>
>
>
> And SM has a big role to play during this to fine tune speed of each team
in
> the same sprint (Not separate)
>
>
>
> Regards,
>
> Amol Patki
>
>
>
> From: Balaji Pasupathy [mailto:call....@gmail.com]
> Sent: 22 July 2011 11:32
> To: BalakrishnanAR
> Cc: ram kumar; Hari Madabhushi Sarangarajan; Kiran Thakkar;
> JOHNK...@hotmail.com; PRAR...@yahoo.com; raj...@thylaksoft.com;
> jeyanthi....@cognizant.com; chi...@cadsindia.com;
> myu_m...@yahoo.co.in; thaniga...@gmail.com;
mail4as...@gmail.com;
> aje...@gmail.com; biju.k...@gmail.com; manic...@gmail.com;
> cmuralim...@gmail.com; amp...@gmail.com; ushaf...@gmail.com;
> pma....@gmail.com; amit....@abknowledgesystems.com
> Subject: Re: CSM - Chennai
>
>
>
> Hi Ramkumar,
>
> Thanks for ur detail thoughts.
>
>
>
> We keep developers and testers busy by having separate sprint for
> development and QA. This works for us for many years now.
>
> The developers finish coding, and UT in sprint 1, during sprint 2, they
fix
> issues that QA finds and also sprint 2 tasks.
>
>
>
>
>
> On Thu, Jul 21, 2011 at 9:26 PM, BalakrishnanAR <youngk...@gmail.com>
> wrote:
>
> Dear friends,
>
>
>
> Nice to see live-discussions.. I hope to bring our live cases soon to the
> table..
>
>
>
> It is not the forward who always scores the goal..
>
> So I think Testers, if they have skill, can also do coding, if they have
> additional time in hand, beyond what is listed below..
>
> Also they can get into Unit Test cases/testing.
>
> Recollect Circle of Influence of Steven Covey..
>
>
>
> Well I guess trust is the base for all this.. And I hope Scrum builds that
> by empowering Self managed teams..
>
> Even in our exercise, we crossed boundaries to achive the objective.. That
> is our natural self..
>
>
>
> Regards,
>
> ARBalakrishnan
>
>
>
> From: ram kumar [mailto:ram....@gmail.com]
> Sent: Thursday, July 21, 2011 7:19 AM
> To: Balaji Pasupathy
> Cc: Hari Madabhushi Sarangarajan; Kiran Thakkar; JOHNK...@hotmail.com;
> PRAR...@yahoo.com; raj...@thylaksoft.com;
> jeyanthi....@cognizant.com; chi...@cadsindia.com;
> myu_m...@yahoo.co.in; thaniga...@gmail.com;
mail4as...@gmail.com;
> aje...@gmail.com; biju.k...@gmail.com; manic...@gmail.com;
> cmuralim...@gmail.com; amp...@gmail.com; youngk...@gmail.com;
> ushaf...@gmail.com; pma....@gmail.com;
> amit....@abknowledgesystems.com
> Subject: Re: CSM - Chennai
>
>
>
> Hi Guys and Balaji
>
> ***Please correct me if i am wrong. following is based on my experience***
>
> Since we are in waterfall mindset, it will be difficult for sometime to
> adapt to scrum. Anyhow developer and tester both will have set of tasks
and
> based on the priority the delivery will occur. It may happen in following
> ways
>
> 1. Tester/Developer no need to wait as they have their own tasks. If
tester
> finds delay in delivery from developer, he can chose other task in
priority
> list/task which have short duration of time(few hours) which is purely
> independent of others.
>
> 2. After the delivery of component to tester the developer can
> a. Write unit test cases for developed component
> b. start coding for next task for the current sprint
> c. raise the issue in daily standup and help other developers
> d. involve in process related activities
> e. do documentation if document writer role is not in the scrum
> f. etc works that is needed for the project/scrum perspective allocated
> for the sprint
>
> 3. During planning meeting itself all the dependencies are identified and
> task priority is set. Also we have daily standup for discussion.
>
> 4. If the developer delivers the component to other scrum without testing
> effort from his own sprint. In this case the overall testing effort will
be
> taken care by second scrum and the developer no need to wait for feedback,
> he can start working on his sprint activities.
>
> 5. If any defect occurs in the delivered component, then the priority of
the
> developer is first to fix the defect, ship the component and continue his
> current task. It is the ideology that "At any point of time the overall
> product can be shippable"
>
> Regards
> R.Ramkumar
>
>
> On Wed, Jul 20, 2011 at 10:43 AM, Balaji Pasupathy <call....@gmail.com>
> wrote:
>
> Hi All,
>
> Nice meeting you all in mail. may be we all can tweet.
>
>
>
> I have a question.
>
>
>
> We all know that a sprint has both Dev and QA activity combined. In that
> case, how we manage the Developer's time while QA is in progress. Sometime
> QA has to run a lot of test case.
>
>
>
> Thanks,
>
> Balaji.P
>
>
>
> On Tue, Jul 19, 2011 at 4:01 PM, Hari Madabhushi Sarangarajan
> <msha...@gmail.com> wrote:
>
> Dear Kiran,
>
>
>
> Thanks for the mail and the excellent class. The presentation looks nice.
> Thanks for your points on applying for PDUs. We will keep in touch with
you
> over linkedin.
>
>
>
> Thanks & Regards,
>
> Madabhushi Sarangarajan Hari (M.S.Hari)
>
> Mobile: +91-9003010311 <tel:%2B91-9003010311> , Chennai, India
>
> On Mon, Jul 18, 2011 at 8:54 PM, Kiran Thakkar <ktha...@yahoo.com> wrote:
>
> Hello everyone,
>
>
>
> I really enjoyed the energetic class. Your energy, humor, and
collaboration
> made this class a great class. I hope you all learned more about scrum and
> could apply to your current project. I will register your name and you
will
> receive an e-mail from scrum alliance prior to 25-July-2011. If you do not
> receive an e-mail from Scrum Alliance by 26-July-2011, please contact me
> directly at ktha...@yahoo.com, Attached please find presentation in .PDF
> and instructions on how to apply for PMI PDUs.
>
>
>
> I am available on LinkedIn and please connect with me under current Penn
> State position Linkedin profile:
> <http://www.linkedin.com/pub/kiran-thakkar-mba-cst/1/256/626>
> http://www.linkedin.com/pub/kiran-thakkar-mba-cst/1/256/626
>
>
>
> If you have questions or need further few days of workshop at your
> organization, please do not hesitate to contact me or UNICOM. Below find
> some useful links as per your requests during the class.
>
>
>
> User story reference material:
>
>
>
<http://www.mountaingoatsoftware.com/articles/27-advantages-of-user-stories-
> for-requirements>
>
http://www.mountaingoatsoftware.com/articles/27-advantages-of-user-stories-f
> or-requirements
>
> Agile Earned Value:
> <http://www.agilekiwi.com/EarnedValueForAgileProjects.pdf>
> http://www.agilekiwi.com/EarnedValueForAgileProjects.pdf
>
> Versionone Survey:
>
<http://www.versionone.com/.../2009_State_of_Agile_Development_Survey_Result
> s.pdf>
> www.versionone.com/.../2009_State_of_Agile_Development_Survey_Results.pdf
>
> Scrum Guide: <http://www.scrum.org/scrumguides/>
> http://www.scrum.org/scrumguides/
>
> My Scrum Trainer profile:
> <http://www.scrumalliance.org/profiles/12300-kiran-thakkar-pmpcst>
> http://www.scrumalliance.org/profiles/12300-kiran-thakkar-pmpcst
>
>
>
> Best Wishes and Keep in touch. Regards,
>
> Kiran Thakkar, MS, MBA, PMP, CST (Certified Scrum Trainer)
>
> E-Mail: <mailto:ktha...@yahoo.com> ktha...@yahoo.com
>
> +1 610-564-7659 <tel:%2B1%20610-564-7659> (Cell)
>
>
>
>
>
>
>
>
>
>
>