Keeping a balance - Re-factoring in Agile Development

You can find an abstract on my company blog at http://kentorjava.com/2013/07/23/refactoring-in-agile-development/

I would like my session to be short and concrete

 
1 favorite thumb_down thumb_up 7 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Would start with basic self-introduction. Then my experience about Agile, development in India and North Europe (short). Later it would to show how a small project leads to big one leading my discussion straight to the topic. 

Some examples architecture/design -- refactoring.

End with some concrete points and then question & answer for a few minutes

 

 

Learning Outcome

To prove that re-factoring is a fact in Agile Development. And all the stakeholders must accept the fact that the velocity cannot be same in all the Sprints.

Target Audience

To all the stakeholders - Developer, Scrum Master, Product Owner/Management

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Since its 20 mins talk, would like to know if you would talk more on the technical aspects or concentrate on working with stakeholders to help them realize the importance of refactoring, hence account it in the budget or cost etc.

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hello,
    I agree refactoring is a critical component of solid development techniques. Are you presenting on any new ideas here or is this an example use case you have been involved in?

    Best,
    joel

    • Muqeet Khan
      By Muqeet Khan  ~  3 years ago
      reply Reply

      All the projects I have been involved there has been discussions about this and we had to make to clear to everyone that we would work in this way. 

      Build - Improve (Refactor) - Build on - Build on - Improve - ...

      We took pause and invested some time. So my presenation would be a case study (simple example) and make the audience especially new ones know about this in advance.

  • Muqeet Khan
    By Muqeet Khan  ~  3 years ago
    reply Reply

    My apologies to you all, I got no notifications on this until I received a mail from Naresh. Anyway here are my comments.

    All the projects I have been involved there has been discussions about this and we had to make to clear to everyone that we would work in this way. 

    Build - Improve (Refactor) - Build on - Build on - Improve - ...

    We took pause (a Sprint though) and invested some time. So my presenation would be a case study (simple example) and make the audience especially new ones know about this in advance. This talk will focus both Stakeholders and the development team. 

    By refactoring I mean to improve the health of the code, design and architecture. Rewrite the parts that have tweaked inorder to fit something in. One important thing is to be realistic and see that you progress with new implementation and also have a healthy code. 

    /MKhan

     

  • Naresh Jain
    By Naresh Jain  ~  3 years ago
    reply Reply

    Request you to please respond to the comment below.

  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    Hi, the key here is what "new" you will be presenting in the conference. I expect audience to have a certain level of understanding / acceptance of refactoring.

  • Doc Norton
    By Doc Norton  ~  3 years ago
    reply Reply

    Muqueet - It will take you only a few moments to copy/paste your abstract from the company blog into the submission system here and you can save everyone else those same moments as we consider your submission. Please do so.

    Having read your abstract, I am not certain I understand what "refactoring" means to you. Can you provide some more detail?

    I know it is only 20 minutes, but I'd like a better sense of how you intend to use that time.

    At the moment, this strikes me as a lightening talk or something to discuss in an open space, not a presentation session.