Hazzan, O. and Dubinsky have posted an interesting article on InfoQ – The Retrospective Practice as a Vehicle for Leading Conceptual Change  about Agile retrospections.

Agile retrospection sessions at the end of each sprint enable knowledge sharing and continuous improvement for software development process. Scrum teams’s self-realization for needed change require a conceptual change for understanding and leading the agile iterations. Small conceptual changes at every retrospection will lead to bigger meaningful change for overall  sofware developement improvement.

Team Participation, Measurements, knowledge sharing and Implementations of fundamental actions drawn to fill these realized gap will lead to self facilitating and improving teams.

Author: Tribhuwan

I am Tribhuwan Negi. I have been a technology evangelist and enthusiast having wide areas of interest in the field of software development and engineering. I have experience in architecting and designing enterprises applications, integration and middle-ware application solutions. I have worked on computational data grids(fabrics), distributed caching, data retrieval systems, complex event processing engines. I have also worked with CADCAM, process engineering and robotic simulations. I have lead teams on complete SDLC cycle. I have worked with start-ups and practiced agile software development. I work on different roles of developer, tech lead, engineering manager, software architect and scrum master. I have Bachelor and Masters Degree in Engineering from Indian Institute of Technology(IIT), Bombay.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: