Project Management | BEP Dev (9to5English)

BEP 322 – Project Management 7: Debriefing User Testing

Business English, IT and Computers, Project Management / April 7, 2018

Welcome back to Business English Pod for today’s lesson on English for project management and debriefing user testing during a software project.

Ask anyone in the tech world and they’ll tell you that user testing is the key to good software development. In fact, that’s not quite true, because the key is actually good user testing. Users don’t always give you exactly the information you need. Or they may not give you all the information you need. For these reasons, you need to be able to do an excellent job of debriefing a user test with the users.

Debriefing basically means talking about an experience. Debriefing helps us understand a user’s thoughts and feelings during their experience with the software. And in software development, that means we can make the necessary changes to improve that experience.

Debriefing a user test effectively might require you to do several things. For one, it’s a good idea to start by setting the focus for the debrief. And later, you might have to bring the user back to that focus area. To get a general sense of the experience, you might ask for overall impressions. And to get more detail, you might ask the user to talk about the process of using the software. It’s also a good idea to acknowledge important issues when they come up.

In today’s dialog, we’ll hear a software developer named Jill debriefing a user test with Carla, an office worker. Jill’s company, OptiTech, has been developing new software for a logistics company where Carla works.

Listening Questions

1. What does Jill say she wants to focus on in the debrief?
2. How does Jill respond to Carla’s suggestion about being able to update a driver’s status?
3. How does Jill respond when Carla mentions that the routes are changing color too soon?

[tp no_translate=”y”]Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3[/tp]

BEP 321 – Project Management 6: Launching User Testing

Business English, IT and Computers, Presentations, Project Management / March 24, 2018

Welcome back to Business English Pod for today’s lesson on English for project management and launching user testing for a software project.

At the heart of every software project is the user. If the user finds the software confusing, or if it doesn’t do what the user needs it to do, what’s the point? For this reason, user testing is an essential part of the development process.

User testing can involve a range of activities. You might watch how users interact with the software. You might track or monitor how they use it. And you might ask them for their opinions. In this way, you collect information and feedback that helps you create the best user experience possible. And just as the software itself needs to be user friendly, so does user testing. If people don’t have a clear idea of what they’re supposed to do during testing, you’ll be wasting an opportunity.

So when you launch testing, it’s important to outline what you’re going to be doing, and what kind of feedback you’re interested in. Because the software is new to the test users, you’ll need to give them clear instructions on how to use it and give them an overview of the main features. You might also find yourself emphasizing key points along the way. After all, it’s much easier to make sure everyone understands upfront than to deal with confused users during testing.

In today’s dialog, we’ll hear Jill, a developer with a software company called OptiTech. They’ve been developing software for a logistics company, and now they are ready to launch the first round of user testing. We’ll also hear Liam, the IT manager for the client, and Carla, one of the test users.

Listening Questions

1. What does Jill say will be the final step in this test?
2. What three aspects of the software does this test focus on?
3. What does Jill emphasize is absolutely necessary for the drivers to do?

[tp no_translate=”y”]Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3[/tp]

BEP 314 – Project Management 5: Scrum Stand-up Meetings (2)

Business English, Meeting English, Project Management / October 7, 2017

Welcome back to Business English Pod for today’s lesson on participating in a scrum stand-up meeting.

Most people I know would agree that the best meetings are those that are short and focused. And that’s exactly how a daily scrum meeting is designed. Scrum is an approach to project management, especially in software development. Every day the scrum team has a short meeting where everyone gives an update.

In a good scrum meeting, those updates should only take 15 minutes. The scrum master keeps everyone focused. That may mean he or she sidebars any discussion that doesn’t relate to the three questions everyone should answer. And what are those three questions that you should answer in a scrum stand-up meeting?

Firstly, you should report what you have been working on. That normally means telling everyone what you accomplished the day before. Next, you’ll let everyone know what you’re going to work on next, or on the day of the meeting. Already you can notice that the meeting focuses on a limited time period.

The third question you’ll answer is whether you face any impediments. An impediment is an obstacle or challenge. Removing those impediments is the job of the scrum master, but your fellow team members may also be able to help. For that reason, you might ask for assistance during the meeting. When everyone’s finished their updates, the scrum master will close the meeting. But not before outlining sidebar topics for discussion after the meeting.

In today’s dialog, we’ll rejoin a scrum meeting at a software company. The team is working on a new piece of software for a logistics company. We’ll hear Jill, the scrum master, and Katherine, who’s giving her daily updates. We’ll also hear from Sam, who you might have heard give his own updates in our last lesson.

Listening Questions

1. What does Katherine say she will be working on today?
2. What is the first impediment Katherine reports?
3. What does Katherine want help with?

[tp no_translate=”y”]Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3[/tp]

BEP 313 – Project Management 4: Scrum Stand-up Meetings (1)

Business English, Meeting English, Project Management / September 30, 2017

Welcome back to Business English Pod for today’s lesson on conducting a scrum stand-up meeting in English.

Not everyone likes meetings, and for good reason. Many meetings are poorly organized and poorly run. But meetings are a necessary part of work and business, especially in project management. For this reason, it’s important that we find ways to have good meetings.

If you’ve worked in software development, especially agile environments, you’ll know about one excellent kind of meeting called a scrum or stand-up meeting. Scrum is an approach to software development that uses cross-functional teams. Each day, the team has a short stand-up meeting where people update others on progress, plans, and challenges.

Whether or not you work in software development, leading a scrum style meeting is a useful experience. You’ll have to do many things that apply to all good meetings. For example, you’ll need to open the meeting and ask for updates. You may also find the chance to suggest collaboration between team members. And the person running the meeting is also responsible for putting aside, or sidebarring, issues that can be discussed after the meeting. These are all techniques that can help you in any kind of meeting, whether you work with scrum or not.

In today’s dialog, we’ll hear Jill, a project manager and scrum master, leading a daily scrum meeting. We’ll also hear two team members, Katherine and Sam. Sam will be first to provide his updates. And, as you’ll hear, Jill will help keep the team focused.

Listening Questions

1. When she opens the meeting, what does Jill suggest they do to stay focused?
2. When Sam says what he is going to do today, what does Jill suggest?
3. What issue does Jill want to “sidebar,” or leave for after the meeting?

[tp no_translate=”y”]Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3[/tp]

BEP 308 – English for Project Management 3: Initial Test Build

Business English, Meeting English, Project Management / June 10, 2017

Welcome back to Business English Pod for today’s lesson on English for project management meetings. In this lesson, we’re going to look at delivering an initial test build to the client.

In our last lesson, we looked at how important it is to set clear expectations with a good project kickoff meeting. But no matter how well you’ve educated the client about your work process, you’ve still got work to do when you deliver an initial test build. You can’t just hand it over to the client and wait for their feedback. It would be nice if project management was that simple, but it’s not. Handing off an initial test build needs to be dealt with carefully.

For one thing, you need to manage the client’s expectations. That means making sure they understand that you’re not delivering a final product. Rather, you’re giving them something to try out, or test. In this way, project management involves collaboration, or working together with a client. And that’s something you will want to emphasize when you deliver the initial test build.

Collaboration is especially important during the testing process. And it’s a good idea to outline the procedures very carefully for the client. If you don’t, then you’re likely to encounter obstacles. When you hand over a test build, you might also discover the client’s needs have changed. Or that they want something new. In this case, it’s important to clearly identify a change in the project scope. And you need to make sure the client understands that there may be cost overruns connected to a change of scope.

In today’s dialog, we’ll hear Martin, a project manager with OptiTech. He’s been leading the development of new software for a logistics company. Martin is having a teleconference with Zara, a manager at the client company, and Liam, their IT manager. They are discussing OptiTech’s initial test build.

Listening Questions

1. At the start of the conversation, what does Martin want to focus on when they look at the initial test build?
2. What does Martin say is the first step in the testing process?
3. How does Martin respond to Zara and Liam’s request for “load tendering tools?”

[tp no_translate=”y”]Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3[/tp]