I've done a variety of software development methods, and they are like governments (Democracy, Communism, Monarchy/Dictatorship). Different goverments produce different cultures and it shows inthe quality of their products.
 
Agile is suituble as for back-end code like file-formats, network-protocols, APIs,frameworks etc. It is great for UX too. The tennants of Agile are:
- Transparency
- Demonstratabilty
- User focus (Stories, and not tasked too far in the future)
- Regular/Frequent/Iterative releases
- Maximization of team talents 
- Minimization of waste
Which apply to any organization or project.
 
*How* you perform or achive those may or may not work well for your organization. Scrum is terrible for disparate developers across multiple timezones. Agile also does not fit well with traditional business contract practices.
Can you run a contract Agilely interally? Sure. The evidence suggests that it will be a better outome than the classic waterfall* methodology.
 
* If you actually read the Waterfall paper, you'll discover that Waterfall as adopted was never what was being suggested. The paper suggested iterative development practices, 20 years before agile. The whole misunderstanding comes from people taking the second illustration out of context. Please read it for yourself (easy read). http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
 
 
Sent: Wednesday, October 05, 2016 at 5:12 AM
From: "Viktor Engelmann" <viktor.engelm...@qt.io>
To: "Bob Hood" <bho...@comcast.net>, "interest@qt-project.org" <interest@qt-project.org>
Subject: Re: [Interest] Agile programming (Was: What don't you like about Qt?)

I don't think that agile programming is a suitable approach for
back-end code like file-formats, network-protocols, APIs,
frameworks etc.

It's okay for quickly evolving UX, but we are talking about
long-term concepts that need to provide stability and IMHO
that requirement is incompatible to agile programming.

If for example you developed a network protocol in an agile way,
in the end all machines would speak different dialects and you'd
never get them to communicate reliably.

just my 2 cents.

Viktor

 
Am 04.10.2016 um 16:28 schrieb Bob Hood:
On 10/4/2016 8:03 AM, Jason H wrote:
I think the bigger issue, that many people have expressed here, but not said as such, is the Qt release cycle is not Agile. As more teams adopt Agile development practices...

http://www.linkedin.com/pulse/agile-dead-matthew-kern

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.

(No intention to hijack the thread.)
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
 
--

 
Viktor Engelmann
Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
viktor.engelm...@qt.io
+49 151 26784521
http://qt.io

Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
Qt World Summit 2016
Qt World Summit 2016 | Pier 27, San Francisco, CA
Experience Exponential Potential on October 18-20
www.qtworldsummit.com
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to