Управление продуктом в стиле Magento Unified Process
Upcoming SlideShare
Loading in...5

Управление продуктом в стиле Magento Unified Process






Total Views
Slideshare-icon Views on SlideShare
Embed Views



4 Embeds 1,278

http://mageconf.com 1152
http://mageconf.local 60
http://dev.mageconf.com 36
http://mageconf 30



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Управление продуктом в стиле Magento Unified Process Управление продуктом в стиле Magento Unified Process Presentation Transcript

    • Magento Product Management style Magento Unified Process Eugene Veselov Project manager, Magento Core Team.
    • 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
    • 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”
    • Plan
      • Magento style leadership ( teamwork )
      • Magento under a microscope ( SDLC of a release )
      • Administrativia ( Change, quality, Time Management )
      • Answering your questions
    • 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
    • Magento style leadership
      • Dynamic 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
    • Magento style leadership
      • Advantages 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 
    • Magento style leadership
      • Architectural 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
    • Magento style leadership
      • Trainings
      • Lots of trainings are help by Magento project team members
      • Knowledge transwer regarding some subsystems in Magento
      • Book Discussions
      • Trends in IT
      • etc
    • Magento under a microscope
    • Magento under a microscope
    • Magento under a microscope
    • Magento under a microscope
    • Magento under a microscope
    • Administrativia New 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 roughly Who: PO, PM (for estimations only) Set right Priority. Who: PO SRS Development Who: BA IG Development Who: SA Create 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 PM
    • Administrativia Change Management Get change, gather all initial data Update SRS Get Initial Approve Complete CR Form Estimate Get Final Approve Add CR to the development plan Plan development
    • Administrativia QM. Deming cycle
    • Administrativia QM. Main Artifacts
    • Administrativia Time Management
      • Yes, we use Gantt diagram.
      • Yes, we use critical path method
    • 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 .
    • Your Questions ?
    • Thank you! !
      • Email me here :
      • [email_address]