Table of Contents · A Supplement to The Past Post · Define an End-to-End Story · Scenario-Based Division v.s. Function-Based Division · Details of A Structured Story · Coach’s Murmur A Supplement to The Past Post I wrote a similar post last year to state what it should look like when you are writing a user story, from the…

An Explosive Argument I had an argument with our Product Owner 2 weeks ago, regarding the difference of task management between us. As a Scrum Master, I thought a Product Owner should have sympathy for first-line executors; prevent context switches from happening as possible as he could to eliminate consumption. For example, I…

Story Points Remains Unchanged In a Sprint In a recent sprint review, we discovered that the selected backlogs were most undone so the burn-down chart reflected the phenomenon with a straight line till the very end as above. …

A Regular Talk That Matters These days I often heard of the department reorganization plan so that some colleagues started worrying about whether there would be a wave of laid-off. I know HR wants to follow one of the rules: maximumly intensify talented people, which was carried out in Netflix — NO RULE RULES. …

Making the Complicated Simple Last time I stated the 5 attributes of a complex system. It’s amazing that we could categorize properties of complicated systems into several groups in convenient for others to further investigate their own internal components. Today I am going to step forward to another topic — Object. Does it seem…

The Simplest Thing Is The Hardest Thing If you would like to construct the highest building of the globe, a sound foundation must be the first consideration in the very beginning, so as the software development. A better up-front design affects the following system development life cycle. However, most companies does not emphasize that but seek for…

An Episode of Retrospective Meeting In the recent sprint retrospective when we were talking about the process optimization of the development. A backend engineer mentioned that now he also took the responsibility to design the overall system architecture that a software architect should do since we did not have this role in our team. …

Knowledge Is Power As Carried Out Inspired by DbC (Design By Contract), I started experiencing the concept from the process of implementing several contracts to clarify whether a client (caller) or a supplier (callee) takes charge of function correctness. I’ve posted several articles recording my learning path about it. Step Inside Design By Contract Nature of Reliabilityuragilecoach.medium.com Implement Design by Contract in Rust

The Servant: A Simple Story About the True Essence of Leadership The Servant: A Simple Story About the True Essence of Leadership [Hunter, James C.] on Amazon.com. *FREE* shipping on…www.amazon.com Its name caught my eyes because my brain suddenly popped up “Servant Leadership” at the first sight. In fact, although the Scrum guide indicates a Scrum master should behave like a servant to coach a team. It does not articulate what the “Servant Leadership” should look like, even if I…