#21

Well, the first thing that I’m doing is implementing a Trello board for the collaboration so we can track the progress of a fairly large number of Ableton sets we’re working on.

We live 90 minutes apart and have very busy lives so getting together in person is infrequent at best. We’re both pretty prolific at starting projects but not so good at sorting out what to do to get them into releasable shape.

So some kind of very informal and mellow version of some of the scrum/agile principles seems to be potentially helpful in keeping track of who is doing what and creating a bit of accountability, albeit in a relaxed way.

I’m still new to this stuff (scrum not music), so trying to muddle my way towards a more “productive “ workflow. Recognizing at the same time that music is fun and not work, but releasing things is part of the fun…

1 Like
#22

That is interesting! I can see how some of the rituals from Scrum might be useful in oganizing communication and accountability. And if you’re trying to more clearly define your process/workflow, Trello should prove to be helpful.
In my mind, one of the big/important features of all forms of Agile is delivering completely working (as in customer facing) parts at short intervals. (Perhaps I have that wrong, but that’s my understanding). To that end, I don’t see how Scrum applies. Really, if you have a well defined process, a clearly defined outcome, and you know the desired outcome will not change, you should probably just do Waterfall. (Or “Scrumfall” if you need to deliver working parts along the way).
Here are some of the methodologies and their purposes (oversimplified) that I’ve been looking into. Maybe one of them might pique your interest…
Waterfall - best when neither process nor deliverables will change (factory/assembly line)
Agile (all forms) - gets management out of workers’ way, anticipates deliverables will change along the way
6 Sigma - a methodology for discovering and fixing hidden waste in complex processes
Lean - Methodology to reduce waste and speed up processes by reducing work in progess (Kanban, the concept not the Agile method, actually comes from Lean)
Design Thinking/Lean Business Startup - A method that incapsulates creativity and iterative process in order to get the (hopefully) best outcome.
You might also find “Design Sprints” interesting. It’s kind of the middle ground between Design Thinking and Agile… sort of…
I’m not an expert in any of the above, so it’s quite possible someone more experienced with them might have a more nuanced view. But I find them all to be interesting, and, in part, applicable. Maybe you will too…

2 Likes
#24

I love this! Covert psy-ops is very Burroughsian…

2 Likes
#25

Thanks! Lots to look into there…

#27

Agile Buzzword Bingo
https://www.bullshitbingo.net/cards/agile/

grafik
grafik.png749×746 11.7 KB

3 Likes
#28

Well, that just sounds wreckless.

6 Likes
#29

Thanks for all the insights!

If I can turn the inquiry in a slightly different direction, does anyone have suggestions for how to coordinate on long distance collaboration, mostly regarding using Ableton, but broader ideas would also be welcome.

I know about Splice although I’ve never tried it…

Thanks!!!

#30

Splice seems to work okay here. We aren’t that active on it (mostly my fault), and it’s I think a learning process for my collaborator to remember to share files with me.

#31

Thanks! Does it have any kind of versioning control?

One of the things I’d most like to see is a way to avoid having to download redundant audio files, and only need to download new additions or changes…

#32

Yeah! I’m not sure how robust it is to, eg, conflicts, but it has versioning control features.

1 Like
#33

People will react with “but don’t store binaries in git!!” but I personally use git for my ableton projects and samples.

Mind you, I only share content with myself and am never in two places at once, so I never deal with merge conflicts. I have a “Studio” folder that is synced between my laptop, basement computer, and my NAS.

Eventually I suspect I’ll have to flatten the repo or just delete the .git folder and restart it but I’ve been doing this for months and it works well for my needs.

1 Like
Github Basics
#34

tools are tools, process tools are process tools like Scrum or Kanban method. For some case it works, for some not. And who and how it help the team or company to implement and support means a lot.
Scrum becomes a buzz or sometimes rude word because of cargo cult - we will work according to sprints and daily standups and all the things be great.

Nobody can’t say without context what is better for your team Scrum, Kanban, any other process without a context. It’s like what is better Reverb of Delay, Rings or Clouds or maybe Rings into Clouds or not?

If you company/team tries to work according to Scrum, a team by itself can share with you roles, events and artifacts, and I hope, Scrum values (which is more important).

Just for youself I can recommend Henrik Kniberg short book Scrum from Trenches (free in digital form https://www.infoq.com/minibooks/scrum-xp-from-the-trenches-2/ or paper copy (poor quantity paper print at amazon). Scrum Guide will be helpful and Open Assessment on scrum.org.

Without context IDK how Scrum can be helpful for attorneys by trade, maybe you create some law products :slight_smile:

2 Likes