Loading ...
Sorry, an error occurred while loading the content.
 

RE: [scrumdevelopment] off-topic (was the three questions of scrum)

Expand Messages
  • Mike Dwyer
    Given the impact that TDD has on both the quality and velocity of delivery, IMO, the QA manager s job becomes that of a collaborative strategist from the get
    Message 1 of 45 , Jun 20, 2005

      Given the impact that TDD has on both the quality and velocity of delivery, IMO, the QA manager’s job becomes that of a collaborative strategist from the get go.   Ken’s posting on Project managers should also apply to QA Managers in an Agile environment.

       

      Michael F. Dwyer

       

      Mike.Dwyer1@...

       

       

      -----Original Message-----
      From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Andrea Zalewski
      Sent: Monday, June 20, 2005 10:20 AM
      To: scrumdevelopment@yahoogroups.com
      Subject: RE: [scrumdevelopment] off-topic (was the three questions of scrum)

       

      Mike, how about QA Managers? 

       

      With the typical QA mindset, I see SO many areas where I can contribute from high level design collaboration, system integration planning and hands on testing.   I would appreciate some of your thoughts for those of us in traditional management roles who want to be pigs, not chickens.

       

      Thank you,

       

      Andrea Zalewski

      615-777-2757


      From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Mike Beedle
      Sent: Tuesday, June 14, 2005 3:46 PM
      To: scrumdevelopment@yahoogroups.com
      Subject: RE: [scrumdevelopment] off-topic (was the three questions of scrum)

       

      Tobias wrote:

      > off-topic question...what is the role of a software architect

      > in an Agile team?Tobias

      Tobias,

       

      One of the challenges with this question is to ask:  what is a “software architect” to begin with?

       

      In my opinion, there is room for an Agile Architect, that:

       

      ·        Does not hijack the development process with architectural activities like mandated

      sequential activities like architectural analysis, architectural modeling, diagramming,

      design reviews, code reviews, etc.

      ·        Keeps coding and participating in a “real way”, not just hand-waving off a white pedestal

      ·        Is active in planning, issue resolution, and mentoring on a daily basis

      ·        Knows how to cooperate and collaborate with others and understands people issues

       

      Not all teams have equal composition, but in any team, there is always “an architect”.

       

      In the best agile teams, the architect role is distributed among all team members.

       

      But in cases where teams are composed of a majority of lesser experienced developers,

      A single highly-experience developer or developers can provide for the architect role.

       

      The Architect role has several functions:

       

      ·        Ensure the conceptual integrity of the system (Fred Brooks, MMM)

      ·        Ensure the construction of the system is possible working with the ScrumMaster

      ·        In some cases, it is ok to have the ScrumMaster also be the Architect (Fred Brooks, MMM)

      ·        Provide knowledge specially on architectural services, patterns, principles, practices

      ·        In Agile teams the Archtiect *must* implement – get his/her hands dirty

      ·        Mentoring other teams members in programming/design issues

      ·        Providing guidance to the ScrumMaster (if he/she is not as technical), in

      understanding component dependency – sometimes that’s important.

      ·        When one or more applications are being programmed, technical architects are

      typically representative in the so-called “Architecture Group”, a group of people that

      meets to standardizes standards, services and components, across multiple teams.

      Etc.

       

      The ultimate goal of the architect is to remove himself/herself from the team by teaching *everyone* in

      the team everything that he/she knows, and ensuring this role is distributed among *everyone* in

      the team.

       

      By the way, this is what we provided for years at Framework Technologies and e-Architects Inc., two of

      The companies I founded in the 90s’,

       

      -        Mike

       



      To Post a message, send it to:   scrumdevelopment@...
      To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...




      To Post a message, send it to:   scrumdevelopment@...
      To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...



    • Mike Dwyer
      Given the impact that TDD has on both the quality and velocity of delivery, IMO, the QA manager s job becomes that of a collaborative strategist from the get
      Message 45 of 45 , Jun 20, 2005

        Given the impact that TDD has on both the quality and velocity of delivery, IMO, the QA manager’s job becomes that of a collaborative strategist from the get go.   Ken’s posting on Project managers should also apply to QA Managers in an Agile environment.

         

        Michael F. Dwyer

         

        Mike.Dwyer1@...

         

         

        -----Original Message-----
        From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Andrea Zalewski
        Sent: Monday, June 20, 2005 10:20 AM
        To: scrumdevelopment@yahoogroups.com
        Subject: RE: [scrumdevelopment] off-topic (was the three questions of scrum)

         

        Mike, how about QA Managers? 

         

        With the typical QA mindset, I see SO many areas where I can contribute from high level design collaboration, system integration planning and hands on testing.   I would appreciate some of your thoughts for those of us in traditional management roles who want to be pigs, not chickens.

         

        Thank you,

         

        Andrea Zalewski

        615-777-2757


        From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Mike Beedle
        Sent: Tuesday, June 14, 2005 3:46 PM
        To: scrumdevelopment@yahoogroups.com
        Subject: RE: [scrumdevelopment] off-topic (was the three questions of scrum)

         

        Tobias wrote:

        > off-topic question...what is the role of a software architect

        > in an Agile team?Tobias

        Tobias,

         

        One of the challenges with this question is to ask:  what is a “software architect” to begin with?

         

        In my opinion, there is room for an Agile Architect, that:

         

        ·        Does not hijack the development process with architectural activities like mandated

        sequential activities like architectural analysis, architectural modeling, diagramming,

        design reviews, code reviews, etc.

        ·        Keeps coding and participating in a “real way”, not just hand-waving off a white pedestal

        ·        Is active in planning, issue resolution, and mentoring on a daily basis

        ·        Knows how to cooperate and collaborate with others and understands people issues

         

        Not all teams have equal composition, but in any team, there is always “an architect”.

         

        In the best agile teams, the architect role is distributed among all team members.

         

        But in cases where teams are composed of a majority of lesser experienced developers,

        A single highly-experience developer or developers can provide for the architect role.

         

        The Architect role has several functions:

         

        ·        Ensure the conceptual integrity of the system (Fred Brooks, MMM)

        ·        Ensure the construction of the system is possible working with the ScrumMaster

        ·        In some cases, it is ok to have the ScrumMaster also be the Architect (Fred Brooks, MMM)

        ·        Provide knowledge specially on architectural services, patterns, principles, practices

        ·        In Agile teams the Archtiect *must* implement – get his/her hands dirty

        ·        Mentoring other teams members in programming/design issues

        ·        Providing guidance to the ScrumMaster (if he/she is not as technical), in

        understanding component dependency – sometimes that’s important.

        ·        When one or more applications are being programmed, technical architects are

        typically representative in the so-called “Architecture Group”, a group of people that

        meets to standardizes standards, services and components, across multiple teams.

        Etc.

         

        The ultimate goal of the architect is to remove himself/herself from the team by teaching *everyone* in

        the team everything that he/she knows, and ensuring this role is distributed among *everyone* in

        the team.

         

        By the way, this is what we provided for years at Framework Technologies and e-Architects Inc., two of

        The companies I founded in the 90s’,

         

        -        Mike

         



        To Post a message, send it to:   scrumdevelopment@...
        To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...




        To Post a message, send it to:   scrumdevelopment@...
        To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...



      Your message has been successfully submitted and would be delivered to recipients shortly.