Business wants what?!
•Transferir como PPTX, PDF•
0 gostou•62 visualizações
Author: Paul Celie Presentation #1 at Magento Meetup Kharkiv 13.04.2018
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (18)
Semelhante a Business wants what?!
Semelhante a Business wants what?! (20)
Mais de Magecom UK Limited
Mais de Magecom UK Limited (20)
Último
Último (20)
Business wants what?!
- 2. WHO. ● Paul, lead developer at Fiyo ● Fiyo is an online webshop in 9 countries ○ 80.000 parts and accessories for appliences ○ 150 employees ○ Own warehouse ○ Both internal and external development team 2
- 3. BUSINESS WANTS WHAT?!. ● Information ● Communication ● Evaluate ● Succeed 3
- 5. INFORMATION, WHY. ● Missing context ● Long distance communication ● Language differences 5
- 6. INFORMATION, WHAT. ● Business owners ● Software ● Processes 6
- 8. COMMUNICATION. ● Backlog ● Planning ● Direct communication ● Be open for ideas 8
- 9. EVALUATE. 9
- 10. EVALUATE. ● Let business owner test before release ● Let business owners test after release ● What went well? ● What could be better? ● Improve 10
- 14. TO SUM UP. ● Information ● Communication ● Evaluate ● Succeed 14
Notas do Editor
- Agenda
- Missing context External developers don’t know the company, they know code Long distance communication No direct contact, so it’s not easy to explain Language differences - Although everybody speaks English, it’s hard to understand each other when it’s not both our native language
- Pick business owners: - Pick people (f.e. managers) who know everything about there department. Keep short lines with these people. Sit together at least every two weeks to keep being informed on what’s going on - Customer service, Logistics, Product management, Purchasing, Marketing, Finance Software: Create an overview of which software you use, which can be involved by what Magento communicates with Adyen, which affects several payment methods, But contact form communicates with Freshdesk which is used by customer service Processes: Get an overview of company processes Know what departments have involved with others and which affects IT
- Backlog We work via agile scrum, but should also work for kanban As you know all information from the previous step, you can work out the issue Try to capsulate it, so it only shows all relevant information, if it affects other systems/processes, please mention it as well Supply the list, so developers can read into it Write in developers language, no business language Planning Involve developers in the planning, planningpoker opens the discussion on what has to be done an how many points it will cost Short commuication lines - Make sure you have contact on a daily base (video), so developers can discuss on a daily base Make direct commuication possible, for most thins one person they can speak to, so they get direct feedback Otherwise developers have to wait and keep issues open. Don’t do it via Jira, it takes too long Be open for ideas Developers have a outside perfect perspecitve on what’s good for the company. Listen to them
- Include business owner in testing process, they’re the only one who know Discuss with both developers as with business owners Write down what has been discussed Discuss after every sprint Notice if things what have been discussed have been improved
- Business is happy as it get feateures delivered as they want They are being heard and involved in the process, but only on parts where the need to be
- Developers are happy They can focus on what they like, developing They get involved in the process where necessary They don’t have to wait too long for answers
- Developers are happy They can focus on what they like, developing They get involved in the process where necessary They don’t have to wait too long for answers
- Agenda