|
Classic piece, love it. But not this.
I'm not sure how many cookies it makes to be happy, but so far it's not 27.
JaxCoder.com
|
|
|
|
|
I liked it at first but it soon got tiresome. The percussion is beyond distracting in a presto piece. It would have been better to just make it a duet with a comparably skilled bassist, because the piece would work well along the lines of a Bach two-part invention, with chords where necessary.
|
|
|
|
|
Perhaps I think it would have been better unplugged, just to metally
I'm not sure how many cookies it makes to be happy, but so far it's not 27.
JaxCoder.com
|
|
|
|
|
|
Honesly: That didn't exactly give mea "moonligtht" feeling.
|
|
|
|
|
|
This changes everything. Game Changer, Ukulele[^]
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
what ?  let my mind process this ...
|
|
|
|
|
I like Beethoven, but I prefer Blue Oyster Cult
Ladies, Fish, and Gentlemen
|
|
|
|
|
Do you consider oysters fish??
|
|
|
|
|
If people understood just these two things about Agile better, then the whole Agile world would be a better place. 
97 Things Every Scrum Practitioner Should Know: Collective Wisdom from the Experts[^]
5 Things Nobody Tells You - 1st entry in the book said...
1. Scrum Will Not Solve Your Problems
Some people hope that Scrum will magically solve their problems, as if it were a silver bullet. But Agile processes like Scrum are more like a mother-in-law looking over your shoulder all the time: they point out all your problems and mistakes, making them transparent. In the end, you have to solve them and do the hard work yourself.
2. Scrum Offers No Benefits When You Only Follow the Process
I have seen teams that did Scrum exactly by the book. They had daily stand-ups, Sprint Planning meetings, Sprint Reviews, Retrospectives, and even Product Backlog Refinement meetings. However, the benefits they reaped from Scrum were minor because they missed the point that Agile is more about being than doing. Becoming Agile requires a mindset change to accompany the process change. Only by embracing the 12 Principles behind the Agile Manifesto and the Scrum Values will Scrum unfold its full potential.
|
|
|
|
|
Scrum is only one of several Agile methods. Please don't use the terms interchangeably, as it highlights ignorance.
|
|
|
|
|
PIEBALDconsult wrote: Scrum is only one of several Agile methods. Please don't use the terms interchangeably, as it highlights ignorance.
Whatevs!
|
|
|
|
|
 Great response.
|
|
|
|
|
He isn't. The author of that piece did.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Quote:
"All Scrum is Agile, but all Agile is not Scrum".
|
|
|
|
|
A rugby union scrum is rarely "agile". 
|
|
|
|
|
That's the cool thing about Agile. It means whatever you choose it to mean. If you implement Agile and it works, you can say, "See? Agile works!" If you implement Agile and it doesn't help, you can say, "We weren't agile enough!"
|
|
|
|
|
Some kind of process is needed, but there's no substitute for a culture of design excellence. If an organization has that, it can use any reasonable process. If it doesn't have that, no process is going to kiss things and make them better.
|
|
|
|
|
|
raddevus wrote: Scrum Offers No Benefits When You Only Follow the Process
In my experience people generally ignore the processes and only use the tools. After a month on any project they think they're agile because they're using Jira.
|
|
|
|
|
F-ES Sitecore wrote: In my experience people generally ignore the processes and only use the tools. After a month on any project they think they're agile because they're using Jira.
That's a very good point and is very often the case. That's how things work a lot of times...you try something, you get some benefit and then you get bored of managing the process so it all slides down the slippery slope into sameness.
|
|
|
|
|
Yeah, it's a mental leap that many people and organizations are unwilling or unable to make.
On a recent project, the PM was touting how "we're going to be agile and do iterative development!"
Six weeks later, when a terribly-written 60+ requirements document arrived, they were surprised when I wanted it broken down into jira tickets for each component, with dependencies between the components referenced in the ticket relationships.
I explained the idea was to have smaller, understandable pieces of implementation that we can cross off the list, while keeping in mind the overall whole. Plus that way, if there were bugs/changes we found when implementing piece X, we can just reopen that one ticket, and not have a stream of issues in a single, overarching ticket which would be impossible to track.
Well, that's too hard, apparently. As we know, email is a legitimate change tracking system.
Sigh.
|
|
|
|
|
only u can solve ur problems
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Which has also been stated as, "No one is coming [to rescue you]." Least of all, a process.
I hadn't seen that Long (Heinlein) quote before. Thanks for that!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
