Agile Manifesto and Follow-ups

on

Agile Manifesto and Follow-ups

its all about valuable process for continious delivery 


Agile community manifesto focuses on human resources and creating effective product devilery mechanism, it suggest  to follow user's stories as a placeholder for conversations, whether it to be creating a new process or by using tools, i.e using face to face communication or defining process.

F2f communication

As name suggest , face to face communication  brings in lots of benefits but challenge of traceability is its biggest fall down.

CONS
  1. Traceability solution :
  • Follow up emails.
  • Summary, key-points, actions and decisions notes.
  • Reports or photo of output.
  1. Time spend on recovering conversation 
  • We recall wrong or mis-remembered information.
  • Mostly without revert implements wrong actions based on above points.
  1. Time wasted on recovering information 
  • Imagine wasting your so precious time spend on crawling emails just trace one task.

Defining Process

Creating labelled process i.e process of all series/action/steps taken in order to achieve a particular end. 

CONS
  1. We perform thousands of task daily, and documenting all of task is waste for both reader and writer.

Slacking

Slack is well known tool, handy for individual and group communication, share materials, search past chat history.

CONS
  1. Risk of becoming "most convenient" method , so covinient that people don't even tend to take followup.
  2. No way to ensure message has be delivered and read by everyone.

All these process provide valuable conversation, interactions and reference points. Processes that help us to inspect our ways of working effectively and drive continues improvements.

Chetan ;-)

Comments

Post a Comment