Having worked on mutliple teams with different methodologies, I am fully aware of the benefits and drawbacks of each. If you read Sutherland's SCRUM book, which I regard has half terrible and half excellent, you'll be able to appreciate my point. The factual reality I am dealing with here is that every two weeks I am punting bugs in our tracker because I'm awaiting for a fix in Qt. In other development processes, this contant punting and lack of transparency in prioritization may go unnoticed.
FWIW, I am as much for Agile as I am against it. As several of you have already stated it has its place but is not a cure-all. However I find that a lot of reluctance with the update is because older developers (including myself) do not like the feeling of micro-management (myself included), others fear the increase of transparency (taking 3 months to do something they could do in 1, or having to admit when development does not progress at an ideal pace). But the fact of the matter is output is increased. But then Agile falls over because it fails in that technically, you can't say when you'll be done a project and thereby how much it will cost, which is abhorrent to business who want to sign fixed-price contracts. What I now see is a lot of hybridization being attempted, which I personally feel is doomed to fail.
Meanwhile Kaizen, the Japanese quality practice of contunious quality improvement seems to be missing from Qt. Given that list of 25+ issues with >= 17 votes, those would be a logical start to achiveing meaningful quality improvements. Those issues should be targeted first since they are affecting the most users. Repeat this every two weeks. Once the outliers are handled then the devs should be able to work on the fun stuff.
PS. If you're hating on Agile because you fear the transparency, or are concerned about your reputation, I think your days are limited. Also see https://www.youtube.com/watch?v=0SARbwvhupQ
Sent: Tuesday, October 04, 2016 at 11:40 AM
From: "Tim O'Neil" <interval1...@gmail.com>
To: interest@qt-project.org
Subject: Re: [Interest] What don't you like about Qt?
From: "Tim O'Neil" <interval1...@gmail.com>
To: interest@qt-project.org
Subject: Re: [Interest] What don't you like about Qt?
I can tell you all from direct experience Agile is not a one-size-fits-all tool. Its a tool, best used in mid-sized to larger organizations trying to build software. Its not at all appropriate for smaller shops. Kanban works just fine in those.
On Tue, Oct 4, 2016 at 8:02 AM, Ronan Jouchet <ronan.jouc...@cadensimaging.com> wrote:
On 2016-10-04 10:28, Bob Hood wrote:Like Spiral from whence it sprung, I think Agile works wonderfully
in certain project profiles. However, not everybody drinks the
all-Agile-all-the-time Kool-Aid®. Contrary to popular religion,
Agile is not the savior of the industry. It's another tool in the
toolbox, not a replacement for all the other tools, and savvy project
managers still apply the development methodology (Spiral, Agile,
Waterfall, etc.) or hybrid -- e.g., Waterfall mixed with Agile
elements -- that makes the most sense for the success of a project.
Just applying full Agile without considering the characteristics of
the project and its intended result is absolutely not a guarantee of
success.
Absolutely. But you're fighting a strawman; Jason was in no way trying
to spread meaningless Agile verbiage / kool-aid, he also explained in
detail what he meant by it. Quoting him, emphasis mine:
On 2016-10-04 10:03, Jason H wrote:My Agile team does two week sprints so we can reorder priorities_______________________________________________
twice a month. **The Qt community has no say (AFAIK) in determining
the priority status, or what is worked on when**. The worst issue I
know of as an example of this is the Canvas bug on iOS (
https://bugreports.qt.io/browse/QTBUG-37095 ). It's been in there
for 2.5 _years_, 17 votes and 36 watchers. Which in my experience is
pretty damn high, though there are older and higher ones. Use the
search string "votes >= 17 AND status != Closed and type = Bug" to
get a list of that and it's brethren.
Which brings up the question, **why isn't the Qt staff using a
similar search to prioritize their backlog on a regular basis?**
I think the **incorporation of a regular search of that nature**
would immensely improve the product. I don't think there is any
**transparency in the selected for fix criteria** ?
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
--
“These last few days are among the happiest I’ve ever ignored.”
-Doug KenneyMDExMDEwMDAgMDExMDAxMDEgMDExMDExMDAgMDExMDExMDAgMDExMDExMTE
gMDAxMDAwMDAgMDExMDExMTAgMDExMDAxMDEgMDExMTAxMTEgMDAxMDAwMD
AgMDExMDAxMTAgMDExMTAwMTAgMDExMDEwMDEgMDExMDAxMDEgMDExMDExMT
AgMDExMDAxMDAg
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
