Learning note — Agile intro and User Story Mapping Ch12

Just finished a course — “Agile at work-Building your Agile team” on Lynda. As more information I got from UX design methods in web development, I heard “Agile” a lot. I knew it’s a kind of form makes designers, data engineer and front-end developers work efficiently. Communication among different positions performs better than the traditional management. A “Light-wegiht” tool for project manager. After taking the course, I briefly knew how it works.

There are many Agile frameworks such as “Scrum”,”Extremely Programming”, “Kanban”,”Scaled Agile Framework(SAFe)” . Scrum and Extremely programming seem to be popular as I saw these two repeatedly appear in web development articles. The most important point in Agile is to clearly redefine one’s role and it’s “self-organised”. Take the framework “Scrum” as an example. There are three roles:

1.Scrum Master — Clear obstacles for developers like a servant not a leader, be able to help all the team members, make sprints burn down chart, “facilitate” meetings and working processes, even misunderstanding among developers This position need to “Facilitate” , not “Control”

2.Product Owner — products backlog, user stories, know the products well(It sound like a UX position to me)

3.Developer — Produce the product, designers. front-end engineers, data engineers and all who build the product

*Working in a same space without blocks makes different positions work face to face. It’s an important set up to make working progress “Agile”. Conversion to contagion.

The product facilitate all members to move forwards, not the pressure of authority. People focus on “Producing Product” by following which roles should do.

On the other hand , Jeff Patton in “User Story Mapping” said that it could be a disadvantage there’s only one person being “Product Owner” as too much things to be done. He suggested to form a “cross-functional discovery team”. Product manager lead members to do product discovery. There are senior engineer, UX designer and product owner in this team. The ideal amounts in this team are 2 to 4 people. Working with subject matter experts, end users, stake holders need communication and facilitation skills. The main mission of a product manager is to identify if the product is “Valuable”,“Usable” and ”Feasible”.

Resources: “Agile at work-Building your Agile team” — Instructor:Dough Rose on Lynda,”User Story Mapping” — Author:Jeff Patton