Better than Agile for managing product development

แชร์
ฝัง
  • เผยแพร่เมื่อ 27 ธ.ค. 2024

ความคิดเห็น • 2

  • @ChristianMilesOnLine
    @ChristianMilesOnLine 3 ปีที่แล้ว +2

    I can't wait for the 150page version of Flow ;-)

  • @johanverbeeck297
    @johanverbeeck297 7 หลายเดือนก่อน

    11:00
    every organization design choice is a choice to
    strengthen certain communication links and you automatically weaken other communication links
    so the organization design question is which of the communication links am i trying to optimize
    if I've got terrible communications between and engineering and manufacturing I need to have an organization structure
    where I have manufacturing people located in engineering and engineering people located in manufacturing
    I need to work on the links that have a lot of information that needs to flow and a high tendency to corrupt that information
    and so rather than the traditional approach of draw a chart and see what the flavor of the month is right I think it's much better
    to go back to basic principles of saying these organization choices are creating needs for communication
    where do I want the really good communications to be
    31:00
    I have the need for mechanical engineering.
    Do I put 5 engineers together in a matrix form or do I put 1 eng in each program ?
    A lot depends on what is the variability of the demand for that service
    if you pretty much have a constant demand for the mechanical engineer on the program,
    enough work to keep the guy full-time busy then probably putting the person on the
    program is going to be the optimum thing to do if you've got real variable bursts
    of demand you'll actually get better performance by aggregating a group of
    people and sort of putting them pulling them on the matrix kind of thing more matrix thing
    They're not sort of an overall answer to that you'll always have
    engineering organizations that have some of these specialist skills and then you do not want to replicate on every team
    The killer in most cases of centralizing resources gets back to the metric question
    classically the centralized resources are being measured by efficiency which
    causes them to operate at a very high level of loading which produces a
    disastrous response time for the projects
    38:00