The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
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.
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.
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.