The weapon of agile management: the story wall

Article source: Official Account-Intelligent IT System.

introduction

Story walls are an effective means of agile management. If used properly, it can bring benefits far beyond what is mentioned in management theory.

Consider the following questions:

  • If a team has a link (such as system testing) with less manpower and low investment, which affects the progress of the project, how can managers find and adjust it in time?

  • If there are many temporary tasks in an iteration, the project manager needs to know the progress of the project every day, including the progress of each story, so as to facilitate the arrangement of temporary tasks, how to quantify it accurately, and make timely decisions and arrangements?

  • How to let everyone on the team know the progress of the team in this iteration without any communication?

  • How to let everyone know the work status of the team as soon as they come to the company every morning, and adjust their work arrangements accordingly?

  • How to let project team members know when to intervene in the work of the project and assess the time needed to complete it?

  • If a member of the project team is passive and has serious delays, but the manager feels embarrassed to criticize directly, or the effect of criticism is not obvious, how to further promote it?


In fact, the above problems may be solved through communication, but if there is a way to speed up the efficiency of communication, or eliminate the communication link, and let the project team members know the situation more accurately, wouldn’t it be better?


The solution is to thoroughly visualize the work, and to advance and allocate resources on the basis of visualization. Every member of the team is able to advance the project, so that everyone will have a further sense of participation, and the project manager is mainly focused on allocating resources. Story walls are a good measure.

 

story wall


How to use:

The team placed a whiteboard near the office seating as a story wall.

After the iteration meeting is complete, team members write each story they are responsible for and post it on the story wall.

After each story is completed, or before get off work each day, each team member updates the status of the story wall.

clear needs

In development

test

grayscale

  

        



   

   


      





  






Everyone updates their own sticky notes in a timely manner. If managers find that most of the sticky notes are in the test column, then the labor or effort of natural testing needs to be increased.


If the above method also requires manpower, you can add:

principal

clear needs

In development

test

grayscale

employee A



employee B




employee C



  

employee D




employee E




employee F




employee G




 

If it is developed for an independent system, you don't need to use the method just now, you can divide it into different modules, and paste the progress bar according to the progress:

principal

module

develop

test

grayscale

online

employee A

Module 1




employee B

Module 2




employee C

Module 3




employee D

Module 4




employee E

Module 5




employee F

Module 6




employee G

Module 7




团队成员每天更新自己的状态,可以在每天的晨会中,对着故事墙来介绍。

 

故事墙能带来很大的帮助,针对项目经理或者团队的管理者。很多问题都能够解决。刚才有提到一些案例,在这就不一一解释了,相信大部门读者看到了之后都可以理解他为什么能解决,并且运用的更好。



公众号-智能化IT系统。每周都有技术文章推送,包括原创技术干货,以及技术工作的心得分享。扫描下方关注。



公众号-智能化IT系统。每周都有技术文章推送,包括原创技术干货,以及技术工作的心得分享。扫描下方关注。

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324471726&siteId=291194637