Magento Product Management style

Magento Unified Process

Eugene Veselov Project manager, Magento Core Team.

1

Facts• ~ 10 unique features in a release

• Release frequency ~3 month

• Team 30+ people

• Developers per feature– 3-4

• Average deviation from deadline +- 5 business days

• Average deviation from planned scope - 1 feature

• Distributed team

2

Four essentials of Good management

• Get the right people

• Match them to the right jobs

• Keep them motivated

• Help their teams to jell and stay jelled

All the rest is administrativia

Т. Demarco “Deadline”

3

Plan

• Magento style leadership (teamwork)

• Magento under a microscope (SDLC of a release)

• Administrativia (Change, quality, Time Management)

• Answering your questions

4

Magento style leadership

Theory Y (according to McGregor)

In this theory, management assumes employees may be ambitious and self-motivated and exercise self-control. It is believed that employees enjoy their mental and physical work duties

5

Magento style leadershipDynamic teams and leaders• 2-4 members team is temporary created for each task(feature) • This team is responsible for entire SDLC of the feature• Dynamic leader is elected among the mini-team• The leader acts as technical leader for his task

6

Magento style leadershipAdvantages of virtual teams

•People work in small teams which jell against their tasks

• It is proved that the most efficient teams consist of 7 (+-2) people

•Team estimates are very precise, about 30%

•Each teammember can try to be a leader and then have rest from leadership

7

Magento style leadershipArchitectural council (AC)

•Consists of 4 most experienced developers and tech PM

•AC members act as dynamic leaders more often, especially in complex or mission critical tasks

•AC is responsible for : researches, technical planning, code review, trainings and etc

8

Magento style leadershipTrainings

Lots of trainings are help by Magento project team members

•Knowledge transwer regarding some subsystems in Magento

•Book Discussions

•Trends in IT

•etc

9

Magento under a microscope

10

Magento under a microscope

11

Magento under a microscope

12

Magento under a microscope

13

Magento under a microscope

14

AdministrativiaNew feature lifecycle

Get initial requirements about a feature.Where: Community, Product owner, support, stakeholders…………Who: All team

Approve feature and add it to the Roadmap, if possible estimate the feature roughlyWho: PO, PM (for estimations only)

Set right Priority. Who: PO

SRS Development Who: BASRS Development Who: BA

IG Development Who: SAIG Development Who: SA

Create WBS according to IG Estimate precisely according to WBS Who : PMCreate WBS according to IG Estimate precisely according to WBS Who : PM

Approve development of the feature and add to the development plan Who: PO and PMApprove development of the feature and add to the development plan Who: PO and PM

15

Administrativia Change Management

Get change, gather all initial dataGet change, gather all initial data

Update SRSUpdate SRS

Get Initial Approve

Complete CR Form Estimate

Get Final Approve

Add CR to the development plan

Plan development

16

Administrativia QM. Deming cycle

17

Administrativia QM. Main Artifacts

18

Administrativia Time Management

• Yes, we use Gantt diagram.

• Yes, we use critical path method

19

Administrativia Time Management

•  In project management, a critical path is the sequence of project network activities which add up to the longest overall duration. This determines the shortest time possible to complete the project. Any delay of an activity on the critical path directly impacts the planned project completion.

20

Your Questions ?

21

Thank you!!

Email me here :

eugene.veselov@magento.com

22