Chapter 327 The truth finally comes to light!
After making up my mind,
Lu Ming stood up immediately.
This can't wait!
He doesn't want to wait until April when the whole network is in chaos.
“This worldview is so exquisite.”
"I'm convinced. Jingyue really understands me."
What else could he do then?
He can only collapse!
So! This time, we have to strike first.
The BUG rescue plan must be arranged now!
He paused, thought for a moment, and opened the team group on Bei Ming's side.
[Lu Ming]: @Zhao Qiliang, Qiliang, how is the recent progress on your side?
[Zhao Qiliang]: Mr. Lu! Progress is going pretty smoothly! The main project is almost finished, and several side projects have been integrated into the main project. We should be able to complete the final tests and run them before the New Year, and then we can directly start tuning after the New Year!
Lu Ming gritted his teeth.
Look!
Look how fluently you speak!
But it hurts so much for me to hear!
This progress is a bit too fast!
Lu Ming closed the group chat, took a deep breath, and murmured...
“…This year is really difficult.”
…
An hour later, Bei Ming's office.
Before it was completely dark, Lu Ming was already standing at the door of the front desk hall with an iced American coffee.
The sound of keyboards clacking and discussions echoed in the hall.
“…Wow.”
“This smell is very familiar.”
Lu Ming walked up the corridor.
Before I even reached the testing room on the second floor, I heard shouts:
"Let's go! Our team won this round of PK!"
"Wait a minute, we'll need to compile statistics later!"
"Why is the record now tied again? We must work hard in the next game!"
"Where's the winning streak we promised? Why are we stuck again?"
Lu Ming paused and frowned.
What's going on?
This argument... sounds a bit too active.
He walked quickly to the door, and before he even entered, he saw several people gathered inside, surrounding two large screens.
On the left is the Jingyue project team, and on the right is the Beishan project team.
There was a rolling list on the big screen!
That’s right, the rankings.
[Comparison table of parallel development efficiency between Whale Leap and Beishan]
Um?
etc.
He narrowed his eyes.
There are various categories below:
[Severity rating] [Reproduction stability] [Main process confirmation time] [Repair cycle estimate]...
Then Lu Ming also saw the information he was interested in,
【Current BUG submission ranking】
Whale Leap Project Team: 212 (+2)
Beishan Project Team: 203 projects (+3)
[Error in this issue: Whale Leap Group 10 items, Beishan Group 12 items]
This is not a leaderboard.
This is——a battle report!!!
Lu Ming's mind buzzed:
"You guys treat BUGs as a competitive sport?!"
In this day and age, are there really people who take the initiative to roll themselves up?
Soon, Zhao Qiliang discovered Lu Ming coming and was shocked.
"Boss Lu, why are you here?"
"Guess why I came?"
Lu Ming took two steps.
"Are you working on some anti-bug plan?"
Zhao Qiliang blinked: "...Ah?"
"I just looked at your rankings. Are the number of bugs also included in the evaluation?"
"What are you doing?"
Zhao Qiliang smiled.
"Mr. Lu, it's like this. Don't we have two project teams now?"
"According to your instructions, we are currently implementing a team competition system!"
Zhao Qiliang spoke with such confidence.
Lu Ming looked confused when he heard this.
"I said it?"
When did I say that?!
Did I let you compete like this?
What I meant earlier was the chaotic civil war!
This is not the kind of competition we have now!
Lu Ming forced himself to remain expressionless:
"……Then what?"
Zhao Qiliang smiled brightly, as if reporting a meritorious service:
"We now have two project teams running in parallel, and each core version will be split into two directions."
"UI process, script performance, task interaction, and system stability were all advanced separately and eventually merged."
"There are also daily working hours, function point delivery ratio, and the efficiency of the main planning document review..."
"Project transparency and full-chain benchmarking have fostered healthy competition and significantly increased development speed!"
"For example, regarding the issue of 'too many plot branches', we can now create two different conclusion structures in the first draft, which is much more flexible than before."
"And there's another benefit to team competition..."
He pointed to the leaderboard and said, "We will proactively check for errors."
“It’s not just bugs! We’ve incorporated a whole set of process metrics.”
"Submission speed, completeness of reproduction instructions, test accuracy, and accuracy of repair time estimation..."
“These are all scoring items!”
"Only when there are scores can there be rankings, and only when there are rankings can everyone move."
"According to my estimation, our overall efficiency has increased by at least 30%!"
Lu Ming: “…”
He understood.
Okay.
I see.
The truth finally came to light!
The reason why the bugs are reduced is finally found!
The fewer bugs, the higher the score!
"I'm not supporting a testing team, I'm supporting an e-sports team, right?"
"Where does your Olympic spirit come from?!"
Lu Ming is almost at his wit's end.
He stood in front of the list and stared at it for a long time.
It's not that you can't compete.
It's how you compete...
How come “fewer bugs” is also considered a core KPI indicator?!
Can you guys please have some basic respect for the developers?
He exhaled slowly, said nothing, and tapped the small words in the column "BUG Quantity Score":
"this……"
"Do you think BUG is really suitable as a comparison indicator?"
Zhao Qiliang was stunned.
"Huh? Why not?"
“Isn’t this the most intuitive reflection of development quality?”
"Whoever has more bugs has a lax process, and whoever has fewer bugs has better risk management..."
"This is a standardized assessment, Mr. Lu!"
He looked so sincere that Lu Ming felt a little numb.
True standardized assessment.
True closed-loop process governance.
But here’s the thing…
If you do this, there will be fewer and fewer bugs.
Lu Ming coughed lightly, thought about his words, and said:
"I'm not saying you're doing anything wrong."
"You are able to manage yourselves, improve yourselves, and form a closed-loop mechanism. This is something that deserves recognition."
"It's just..."
"BUGs, for example, can't simply become negative indicators."
Zhao Qiliang was stunned.
"How do you say that?"
Lu Ming tapped his chin with his fingers and said slowly:
"You're efficient, that's for sure! But have you ever considered that there's something fundamentally wrong with this?"
“Competition is not a problem, and team benchmarking is not a problem.”
"But now you're turning bug data into indicators, KPIs, and reverse incentives. If a problem occurs, points will be deducted. Who would dare to do it in the future?"
"You think you can still maintain your enthusiasm now because you are still working on the early stages of the architecture."
"But as your development progresses..."
“Once you enter the mid- to late-stage functional integration phase, you’ll see the team start to shirk responsibility and be hesitant to take risks.”
"If you wipe them all out at once, those developers won't dare to make mistakes!"
"Especially now, our game is so large, who can guarantee that there will be no bugs?"
"So, what I mean is that during the development process, we should allow trial and error, allow iteration, allow you to make mistakes once, and then find a more reasonable way to write it."
“This is the minimum respect for developers.”
"If you make reducing bugs your goal, you won't be able to develop the game any further."
“You think you’re saving time, but you’re actually cutting off your own possibilities.”
Zhao Qiliang nodded seriously:
"Mr. Lu, you are right."
"Then can I understand it as..."
"We can continue to compete and rate, but should we remove the 'number of bugs' factor from the evaluation process?"
"right."
"That's what I mean!"
Continue read on readnovelmtl.com
