Switching to Open Live Writer and WordPress to get my blog back off the ground.
What am I talking about? It was UNDER ground.
This workflow is from the podcast episode that Scott Hanselman posted on Jan 16, 2020 https://hanselminutes.com/719/myself-its-not-weird-at-all
One of the techniques that is used in Agile development is minimal documentation. In order to support this, bullet points and checklists are quite helpful.
Below is an example of my podcasting setup documentation. Included is a bullet list of things that needed to be collected ahead of time. I have also included a checklist that I use when creating a new recording session.
As you can see, the information included would not be considered adequate documentation, by itself. It is plenty to use as a starting point. Each piece of hardware and software has its own documentation if someone is interested. It also shows how each of the pieces works together without being overwhelming.
Think about the things that you do every day.
I’m sure you can put together a checklist for each. Presidents leave advice for their successor (https://www.nytimes.com/2017/01/20/us/politics/letters-from-presidents-to-successors.html), why shouldn’t managers?
I wish my predecessor had left me check lists like these, my first few months as a manager would have been much easier.
Audio Tecnica ATR-2100 http://www.audio-technica.com/cms/wired_mics/b8dd84773f83092c/index.html
Neewer microphone boom https://www.amazon.com/gp/product/B01GRMF5ZE/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1
Podium Free (32 bit) http://zynewave.com/podium-free/
winLAME https://winlame.sourceforge.io/
Download Podium Free from http://zynewave.com/podium-free/
Unzip and install the 32 bit version. This version is able to load a larger number of plugins, which you may choose to use later.
Once installed, run the application
Download winLAME from https://winlame.sourceforge.io/
Run the installer
You will use this later
[ ] Select Project – New Project
[ ] Edit the project name
[ ] Configure the audio to match your input and output devices
[ ] Click Create Project
[ ] Underneath the “Master” track right-click the mouse button and select Add New Track
[ ] Enter a track name of Mic with Effects
[ ] Check Use as group track
[ ] Click OK
[ ] Right-click the mouse button on the “Mic with Effects” track header and select Add New Child Track
[ ] Enter a track name of Mic (Raw)
[ ] Click OK
[ ] On the Mic (Raw) track, click the input dropdown and select Audio In 1 + 2. This will record from your microphone, in stereo.
[ ] Save your project. Project – Save Project
[ ] Click on the grayed out R button on the Mic (Raw) track. It will become bold
[ ] Click on the grayed out circle button at the bottom of the screen (this is the record “master arm” button. The Mic (Raw) track will be highlighted in red.
[ ] Click the triangle “play” button to begin recording.
[ ] Press the square “stop” button to stop recording.
[ ] Select File – Export to Sound File…
[ ] Click Export
[ ] Type in the name of the file you would like to save. (Leave the extension as .WAV)
[ ] Open winLAME
[ ] Select the file that you saved above
[ ] Convert the file to mp3
This version will require you to purchase Reaper. It is $60 for non-commercial use. The time saved in the updated checklist will more than make up for the purchase price.
Reaper (64 bit) http://www.reaper.fm/download.php
ULTRASCHALL Podcasting Extensions for the REAPER DAW https://github.com/Ultraschall/REAPER
Download Podium Free from http://www.reaper.fm/download.php
Download and install the 64 bit version.
Once installed, run the application
Follow the directions here http://ultraschall.fm/install/
[ ]Start Reaper (x64)
[ ] Select Podcast – Project templates – Ultraschall Soundboard
[ ] Click no when prompted to save unsaved project
[ ] Configure the audio to match your input and output devices (Podcast – Audio device settings…)
[ ] Click on the dard red circle at the top of the screeen
[ ] Speak
[ ] Press the square “stop” button to stop recording.
[ ] Podcast – Export – Start export assistant
[ ] Follow the steps
[ ] Export MP3
[ ] Select directory
[ ] Enter name
[ ] Select output format (MP3 (encoder by LAME project) – You may be prompted to download and install required libraries
[ ] Click on Render 1 file…
[ ] Optional MP3 customization
[ ] Edit ID3V2 Metadata
[ ] Fill in fields as appropriate
[ ] Click OK
[ ] Add an image
[ ] Click Open Project Folder
[ ] Copy an image to this folder – Rename it to be the same name as the project
[ ] Finalize MP3
Links:
http://www.ilovefreesoftware.com/28/windows/mp3/music-production-podium-free.html
Welcome to my page.
Here, I will be posting some ideas about applying agile development ideas to managing other types of activities. Some may be life management. Others may be more typical management in a business organization. I have seen these ideas applied in business, religious and volunteer organizations.
This blog will be modeled after the way some electronic book authors work. I, like they, will offer you membership into an “Early Access Program”. Some of the chapters will be incomplete. Others could use some editing. Something is better than nothing. Don’t let great get in the way of good.
Please join me in this adventure where we can both Manage with Agility
How can you apply agile to your meetings?
In the agile methodology known as SCRUM, there is a daily stand up meeting, that lasts 15 minutes.
In that 15 minutes the team is supposed to let each other know what they are doing.
Each person has three things to say. What they did yesterday. What they will do today. Anything that is getting in the way. The meeting is over after everyone speaks or 15 minutes is up. Whichever comes first. That’s right. If time runs out before you speak, you missed your opportunity for the day. After a few “incomplete” meetings, developers learn to cut to the chase and get their items discussed more quickly.
I’m not saying that you should necessarily go around a room full of managers and executives what they did yesterday etc. But there are some concepts that will make any meeting run better.
The first is to have a known reason for the meeting. If there isn’t a known purpose for the meeting don’t have it.
Wow, now that I have that off of my chest, let’s get to the point.
When you are planning a meeting (you are planning aren’t you) you need to have an agenda. An agenda is more than a list of topics. It has to include when each topic will begin and end.
Bad “Agenda”
| Topic 1 |
| Topic 2 |
| Topic 3 |
| Topic 4 |
What’s bad about this? Everyone knows what will be discussed. Don’t they?
When will people know when a topic has taken too long? Will you be able to accomplish everything in the time you have scheduled? What if someone has to arrive late? Or leave early? Will they be able to catch the topics that they need to?
A better agenda will be what is called time-boxed. It will have start and end times. And you should stick to them.
Better Agenda
| Welcome and ground rules | 9:00 | 9:05 |
| Topic 1 | 9:05 | 9:15 |
| Topic 2 | 9:15 | 9:25 |
| Topic 3 | 9:35 | 9:45 |
| Topic 4 | 9:45 | 9:55 |
| Parking lot | 9:55 | 10:00 |
There are a few things to point out. First is the addition of Welcome and parking lot items.
The welcome item will allow you to greet everyone in the meeting and discuss any ground rules for the meeting. Some of the most important ground rules are to stick to the agenda. An item that runs over should be noted in the parking lot, so that the meeting can proceed on schedule. Any ideas that are not directly related to the topic of the meeting should also be noted on the parking lot.
You will also note that I gave each item equal amounts of time. If you are new to agendas, this is a good way to start. Believe me. Even this rough approximation is more than many meetings have. If you realize that you do not have enough time for a topic, it is better to realize it before you invite other people to the meeting. You may realize that you need to cut down on the number of topics that can be covered. You may also decide that you need to extend the length of the meeting. Please don’t schedule a meeting longer than 2 hours, unless absolutely necessary. People tend to stop listening after about 90 minutes.
The parking lot items can be addressed at the end of the meeting. Some might need further follow up (another meeting possibly), while others may have actually been answered during the meeting. Any open items should be included in the meeting write up. (More about meeting write-ups in another post). If the parking lot is empty, the meeting is over and everyone gets some time back.
Once the meeting is over leave. Even if there are follow up discussions, do them elsewhere.
After a few meetings like this, you will start to see improvements in how your meetings run. People will start to show up on time. They will be prepared to discuss the topic(s) of the meeting. They will know when they can leave and get to the next meeting. That’s right. The “rule of two feet”. If you don’t have anything to add or gain from a meeting, use your two feet and leave.
The first step of being agile is to DO SOMETHING.
I’ve got the domain.
I’ve got the web site.
I’ve got ideas.
I’ve made my first post.
It will grow. It will change. It IS.
There’s no such thing as coulda, shoulda, or woulda. If you shoulda and coulda, you woulda done it. Pat Riley
https://www.brainyquote.com/quotes/quotes/p/patriley147936.html
First, a little bit about where I work.
My employer is in an “old-school” industry, doing things in a “new-school” way. That means that they rely on IT to help get things done. Guess where I work. You got it IT.
In many software shops, each project has a definite start and end. The typical end of a project is when the software goes into production. That type of project is typical when doing work on a contract basis.
For an in-house development team the project never “ends”. There are always changes and enhancements to be made. The end of a project is when the last user stops using it.
That led me to think that in-house software development is closer to building an assembly line (of custom automobiles) than it is to building a bridge.
When designing and building a bridge, there are certain constraints, just as there are when building an application with an “to production” ending.
There are different constraints when building applications with an “into production” approach. You have to remember that the assembly line that you build will have to be maintained and modified as it is used.
| To Production | Into Production | |
|---|---|---|
| Location | Close to building materials and construction labor | Close to product materials, product shipping and operating labor |
| Land | Just enough to fit the factory and the construction equipment | Enough land for employee parking and keeping open the option of future expansion |
| Assembly | Use the fastest method of assembling the factory and the production line with the latest equipment available. (Welds and rivets) | Use a reasonable method that allows for future expansion and flexibility, both in the facility and the production line, using equipment proven to be reliable (Bolts) |
| Planning | Focus on this factory. Once a skill is no longer needed, they are off the plan. | Focus on every factory. Once a skill is no longer needed here, what are they working on next. “When can I get a skill from another factory we are building? I need them here.” |
On November 13, 2014, it became official. I now have “Manager” in my job title.
The news came out in a bulk announcement of changes from H.R. The announcement included firings, staff realignment and oh yes, by the way 2 promotions.
Talk about trial by fire. Quickly my director was inundated with people asking questions. He calmly directed them to speak to their new bosses. (They stopped reading when they saw that people had been fired)
I met with my 4 directs as soon as I could. I had to get some information myself before I could pass anything on to them. Our jobs are all “safe” for now. There is no telling what any company will do 6 months down the road.
People had been including me in their weekly status reports and I had been looking at the stack of upcoming projects for a few weeks now. Suddenly they take on new meaning.
In the next few weeks I’ll have the experience of writing and delivering employee reviews, salary adjustments and bonus calculations.
Why do I have the sudden urge to open Microsoft Project?
Well, my previous boss’s last day was today. I’m back filling, along with a co-worker, until a new person is hired.
Today she went through her pile of current and upcoming projects and divvied them up between the two of us. Then the meeting requests started flying in.
I commented on the research of a co-worker who just started a few weeks ago. I can tell I have to start at square one with explaining the business.
I had a meeting where we discussed a coding issue that seems to have been 18 months in the making. Why was I so calm? I guess it’s because I wasn’t being blamed for anything. We’ll have to work that issue out.
It’s good practice. I’d rather make my mistakes while people aren’t expecting as much from me.
I’m going to have to back out of my usual role of doing the work and take on a different role of planning the work.
I’m sure there will be challenges. That’s what I like. I’ve actually had some practice with this before. I filled in when the previous manager got re-assigned. I had even applied for the position, but they were looking for serious management chops. I couldn’t complain about who they chose. She was stellar. She brought in many process improvements and was a great mentor for the time that she was here.
I hope to get a solid definition of my job duties soon.
Until then “I’m not a manager, but I play one at work” (AGAIN)
Brad's Random Thoughts 