BEP 313 – Zarządzanie projektami 4: Spotkania Scrum Stand-up (1)

BEP 313 - Angielski w projektach 4: Spotkania Scrum Stand-up 1

Welcome back to Business English Pod for today’s lesson on conducting a scrum stand-up spotkanie w języku angielskim.

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 zarządzanie projektami. Z tego powodu, 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. Na przykład, 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.

W dzisiejszym oknie dialogowym, usłyszymy 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. I, as you’ll hear, Jill will help keep the team focused.

Pytania do słuchania

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?

Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3

BEP 308 – Angielski dla zarządzania projektami 3: Wstępna kompilacja testowa

Kapsuła z językiem angielskim biznesowym 308 - Zarządzanie projektami w języku angielskim - Wstępna kompilacja testowa

Witamy ponownie w Business English Pod na dzisiejszą lekcję Angielski na spotkania dotyczące zarządzania projektami. W tej lekcji, zajmiemy się dostarczeniem klientowi wstępnej wersji testowej.

W naszej ostatniej lekcji, przyjrzeliśmy się, jak ważne jest, aby dobrać jasne oczekiwania spotkanie inauguracyjne projektu. Ale bez względu na to, jak dobrze poinformowałeś klienta o swoim procesie pracy, nadal masz wiele do zrobienia, gdy dostarczysz pierwszą wersję testową. Nie możesz po prostu przekazać go klientowi i czekać na jego opinię. Byłoby miło, gdyby zarządzanie projektami było takie proste, ale nie jest. Z przekazaniem początkowej wersji testowej należy postępować ostrożnie.

Dla jednej rzeczy, musisz zarządzać oczekiwaniami klienta. Oznacza to upewnienie się, że rozumieją, że nie dostarczasz produktu końcowego. Raczej, dajesz im coś do wypróbowania, lub test. W ten sposób, zarządzanie projektami wymaga współpracy, lub współpracując z klientem. I to jest coś, co warto podkreślić, dostarczając pierwszą wersję testową.

Współpraca jest szczególnie ważna podczas procesu testowania. Dobrym pomysłem jest bardzo dokładne nakreślenie procedur dla klienta. Jeśli nie, wtedy prawdopodobnie napotkasz przeszkody. Przekazując wersję testową, możesz również odkryć, że potrzeby klienta uległy zmianie. Albo że chcą czegoś nowego. W tym przypadku, ważne jest, aby jasno określić zmianę w zakresie projektu. Musisz też upewnić się, że klient rozumie, że mogą wystąpić przekroczenia kosztów związane ze zmianą zakresu.

W dzisiejszym oknie dialogowym, usłyszymy Martina, kierownik projektu w OptiTech. Kieruje rozwojem nowego oprogramowania dla firmy logistycznej. Martin ma telekonferencję z Zarą, kierownik w firmie klienta, i Liam, ich menedżer IT. Omawiają wstępną wersję testową OptiTech.

Pytania do słuchania

1. Na początku rozmowy, na czym Martin chce się skupić, patrząc na początkową wersję testową?
2. To, co mówi Martin, jest pierwszym krokiem w procesie testowania?
3. Jak Martin odpowiada na prośbę Zary i Liama ​​o „załadowanie narzędzi przetargowych?”

Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3

BEP 307 – Angielski dla zarządzania projektami 2: Otwarcie spotkania (2)

Kapsuła z językiem angielskim biznesowym 307 - Zarządzanie projektami w języku angielskim - Otwarcie spotkania 2

Witamy ponownie w Business English Pod na dzisiejszą lekcję, which continues our look at a spotkanie inauguracyjne projektu.

Anyone who’s been involved with projects should know just how important it is to have good communication with a client. And good communication starts right at the beginning, at a project kickoff meeting. That’s when you’ll have the chance to make sure a client understands how you work and how the project should run.

W naszej ostatniej lekcji, we looked at some of the basics that you need to cover in your first project meeting. Dzisiaj, we’ll look at some more ways of increasing your chances of avoiding problems and ensuring that a project runs smoothly. W wielu przypadkach, it can be a good idea to actually bring up potential obstacles in your meeting. If you see something that might impact the timeline or the budget, you can let the client know about it. And that might mean that you have to educate the client about your work process.

When you educate a client about your development process, you might find yourself using too much technical language. But if you want the client to really understand, you might have to rephrase that information in simpler terms. Oczywiście, you don’t want to focus too much on potential problems. And for that reason you should know how to redirect a discussion away from problems and toward other issues. Na przykład, you might need to ask the client for important information to get the project started.

W dzisiejszym oknie dialogowym, we’ll rejoin Martin and Jill. Their company, OptiTech, is starting a new project to develop software for a logistics company. Martin and Jill are kicking off the project by holding a teleconference with Zara, the manager of the client company, i Liam, ich menedżer IT. In this part of the dialog, Martin and Jill are making sure Zara and Liam understand potential obstacles and the development process.

Pytania do słuchania

1. What does Martin say is the cause of some potential obstacles?
2. What is Jill’s simple explanation of a technical idea that Zara didn’t understand?
3. When Martin redirects the discussion away from obstacles, what does he say he wants to discuss?

Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3

BEP 306 – Angielski dla zarządzania projektami 1: Otwarcie spotkania (1)

Kapsuła z językiem angielskim biznesowym 306 - Zarządzanie projektami w języku angielskim - Otwarcie spotkania

Welcome back to Business English Pod for our new series on English for project management. For our first lesson we’re going to look at a kickoff meeting at the start of a project.

Whether or not you’re a project manager, you surely know that every project is a unique and complex process. Seeing a project through to completion, on time and within budget, takes a huge range of people skills and business know-how. And sometimes during a big project it might feel like everything is working against successful completion.

But there are ways to minimize some of these challenges. This is particularly true at the beginning of a project when it’s important to make sure you get off to a good start. Dla jednej rzeczy, you’ll need to meet with the client to make sure the ground rules of the project are clear. W przeciwnym razie, you’ll be dealing with confusion mid-project. Kicking off a project effectively also means outlining protocols, or important procedures, and explaining lines of communication. W sumie, when a problem or challenge does arise, everyone should know exactly who to talk to and how to make the necessary changes.

The kickoff meeting is also a time for everyone to make their priorities clear. If you are the client and sticking to the timeline is more important than keeping to the budget, you should make that known right from the start. Oczywiście, there may be competing priorities. And as a project manager, you may have to manage client expectations carefully, which might involve setting some conditions when you agree to something.

W dzisiejszym oknie dialogowym, we’ll join Martin and Jill, who work for a software company called OptiTech. Their company is holding a teleconference to kick off a project to develop custom software for a logistics company that will help them manage and track shipments. Martin is the project manager, while Jill is the lead developer. On the call, we’ll also hear from Zara, a manager at the logistics company, i Liam, ich menedżer IT. Razem, they are all trying to get the project off to a good start.

Pytania do słuchania

1. How does Martin say that Jill should deal with technical issues?
2. What does Zara emphasize as her company’s priority in the project?
3. Near the end of the conversation, what condition does Martin attach to the successful management of the timeline?

Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3

BEP 303 – Podróż służbowa 6: Omawianie zmian strategicznych

BEP-303-Business-English-Lesson-Discussing-Strategy-Change

Witaj zpowrotem w Kapsuła z językiem angielskim biznesowym for today’s lesson on discussing strategic change.

The world of business and the economy are constantly changing. And businesses need to respond with their own changes, or risk getting left behind. But change can be difficult both for people and for organizations. As a leader of people in a changing organization, you might face resistance. So you need to be able to manage change well. And that often involves effective discussions with others in the company about strategic change.

Oczywiście, change is easier when the general feeling in a company is positive. And that’s why you might need to gauge morale when you’re talking with others. That will help you figure out how to manage the change. But managing change doesn’t mean promising that it will be easy. Zamiast, you should carefully warn others about possible difficulties.

Another thing you should do is to be clear about messaging. Change is a lot easier if everyone has the same idea about what’s happening and why. It’s also a lot easier if you can show the benefits of the changes. And that’s why you should talk about change as an opportunity that can help the company, and its people. If you can successfully show people that change is an opportunity, then you should get a positive response when you ask people whether they’re committed to the changes at hand.

W dzisiejszym oknie dialogowym, we’ll hear Cam and David, who work for an American clothing company called Boston Vintage. David is the manager of the company’s Shanghai office. Cam is a production manager who is visiting China to meet with the company’s staff and look at new production facilities. In an earlier conversation, Cam told David that the company has made the strategic decision to focus on Southeast Asia rather than China.

Pytania do słuchania

1. How does Cam gauge morale, or ask about the overall feeling among staff?
2. What is the basic explanation for the change that Cam wants David to communicate?
3. According to Cam, why is this change an opportunity for David?

Premium Members: PDF Transcript | Quizzes | PhraseCast | Lesson Module

Download: Podcast MP3