tag:blogger.com,1999:blog-684183198890094283.post2451110983065006036..comments2023-11-05T06:12:59.718-05:00Comments on S.Lott-Software Architect: Breaking into AgileS.Lotthttp://www.blogger.com/profile/06337323642834330176noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-684183198890094283.post-19951042349546734722009-10-22T20:05:22.782-04:002009-10-22T20:05:22.782-04:00"variable in a formula"
Warning Pontifi..."variable in a formula"<br /><br />Warning Pontification<br /><br />The "real world" usually involves more than one equation with one variable. However, ...<br /><br />If you are lucky, your system is time invariant.<br /><br />If you continue to be lucky, you will have n equations with n unknowns. <br /><br />If you continue to be lucky, all your equations will be linear.<br /><br />If you continue to be lucky the inverse matrix of your linear equations won't be zero.<br /><br />If you continue to be lucky, your numbers are well behaved and you don't have to do partial pivoting during your inverse matrix operation.<br /><br />If you continue to be lucky, just stop working and buy a lottery ticket.<br /><br />In the "real world", our systems are often time variant and governed by non-linear equations which may or may not be constrained. To get a quick feel for how truly difficult these problems are, consider scheming<br /><br />www.mpri.lsu.edu/textbook/Chapter6.htm.<br /><br />Software developmnet is at least an order of magnitude harder because in addition to dealing with the technology, you have to deal with business constraints intermixed with the human condition.Robert Lucentehttps://www.blogger.com/profile/12434992671749777590noreply@blogger.comtag:blogger.com,1999:blog-684183198890094283.post-15376482524001921752009-10-22T17:55:55.585-04:002009-10-22T17:55:55.585-04:00Looking forward to hearing your thoughts of Lean P...Looking forward to hearing your thoughts of Lean Principles applied to Software Development.Dean Goodmansonhttps://www.blogger.com/profile/10314983135063028209noreply@blogger.comtag:blogger.com,1999:blog-684183198890094283.post-83368309970347251742009-10-22T14:02:05.121-04:002009-10-22T14:02:05.121-04:00Fantastic post Steven. I agree that as you put it,...Fantastic post Steven. I agree that as you put it, we need to, "close the gap between Problem Domain and Solution Domain by letting programmers understand the problem," and then helping them solve it. On the other side of the equation, managers need to understand the challenges involved in solving that problem. I've seen all sorts of problems arrise due to massive communication issues, typically with management not understanding what is going on, why things are taking so long, etc. The onus is on the Team in this case to help management understand their side of the problem, the issues involved in solving it, and solutions they are working toward.<br /><br />As you point out, the Agile Manifesto talks about individuals and interactions over processes and tools. And to use a cliche, communication is a two-way street.Robert Dempseyhttps://www.blogger.com/profile/00826208059090783477noreply@blogger.com