GoConqr has a new look! Let us know what you think.

Flashcards

Dad Certification(Part 1)

Carlos Andres Garcia Dirección de Proyectos Certificado PMP (Dirección de Proyectos) English 200 cards

Cards in this deck (200)

  1. 1Which ones are The Lean Software development principles?-Eliminate Waste
    -Build In quality
    -Create Knowledge
    -Defer Commitment
    -Deliver Quickly
    -Respect People
    -Optimize the whole
    (book recommended Implement Lean software development of mary and tom poppendieck)
  2. 2Which kanban principles , DAD consideres are critical to success?- Visualize workflow
    - Limit work in progress
    - Make work flow
    (book recommended kanban of David J Anderson)
  3. 3Which are the scaling factors?Team size
    Geographic Distribution
    Regulatory compliance
    Domain Complexity
    Organization distribution
    Technical Complexity
    Enterprise Discipline
  4. 4Formal Change management is like CCB on PMP?The answers is yes, but without many bureaucracy
  5. 5Which are the four agile values? (part of being agile)1. Individuals and Interactions Over Processes and Tools
    2. Working Software Over Comprehensive Documentation
    3. Customer Collaboration Over Contract Negotiation
    4. Responding to Change Over Following a Plan
  6. 6Which is the first principal of agile development?(part of being agile)Customer satisfaction through early and continuous software delivery
    – Customers are happier when they receive working software at regular intervals, rather than waiting extended periods of time between releases.
  7. 7Which are the second principal of agile development?(part of being agile)Accommodate changing requirements throughout the development process
    – The ability to avoid delays when a requirement or feature request changes.
  8. 8Which are the third principal of agile development?(part of being agile)Frequent delivery of working software
    – Scrum accommodates this principle since the team operates in software sprints or iterations that ensure regular delivery of working software.
  9. 9Which are the Fourth principal of agile development?(part of being agile)Collaboration between the business stakeholders and developers throughout the project
    – Better decisions are made when the business and technical team are aligned.
  10. 10Which are the Fifth principal of agile development?(part of being agile)Support, trust, and motivate the people involved
    – Motivated teams are more likely to deliver their best work than unhappy teams.
  11. 11Which are the Sixth principal of agile development?(part of being agile)Enable face-to-face interactions
    – Communication is more successful when development teams are co-located.
  12. 12Which is the Seventh principal of agile development?(part of being agile)Working software is the primary measure of progress
    – Delivering functional software to the customer is the ultimate factor that measures progress.
  13. 13Which is the Eighth principal of agile development?(part of being agile)Agile processes to support a consistent development pace
    – Teams establish a repeatable and maintainable speed at which they can deliver working software, and they repeat it with each release.
  14. 14Which is the Ninth principal of agile development?(part of being agile)Attention to technical detail and design enhances agility
    – The right skills and good design ensures the team can maintain the pace, constantly improve the product, and sustain change.
  15. 15Which is the Tenth principal of agile development?(part of being agile)Simplicity
    – Develop just enough to get the job done for right now.
  16. 16Which is the Eleventh principal of agile development?(part of being agile)Self-organizing teams encourage great architectures, requirements, and designs
    – Skilled and motivated team members who have decision-making power, take ownership, communicate regularly with other team members, and share ideas that deliver quality products.
  17. 17Which is the Twelfth principal of agile development?(part of being agile)Regular reflections on how to become more effective
    – Self-improvement, process improvement, advancing skills, and techniques help team members work more efficiently.
  18. 18What does "That is, while there is value in the items on the right, we value the items on the left more. "mean?No quiere decir que los items de la izquierda no presenten valor o que no se hagan, solo que los de las izquierda tienen se valoran mas.
  19. 19Where is the agile manifesto?www.agilemanifesto.org
  20. 20Where We Should Extend Agile Thinking?- Thinking in Solutions, not just software
    - Thinking Stakeholders, not just customers
    - Thinking The organizational ecosystem,
    not just development teams
  21. 21Which are the four Disciplined Agile Manifesto values?1. Individuals and Interactions Over Processes and Tools
    2. Consumable solutions(Working Software) Over Comprehensive Documentation
    3. Stakeholder(Customer) Collaboration Over Contract Negotiation
    4. Responding to Change Over Following a Plan
  22. 22Which are the changes between agile manifesto values and disciplined agile values?- Change Working Software to Consumable solutions
    - Change Customer Collaboration to Stakeholder Collaboration
  23. 23Which are the First principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Our highest priority is to satisfy the stakeholder(Customer) through early and continuous
    delivery of valuable solutions.
  24. 24Which are the Second principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Welcome changing requirements, even late in the solution delivery lifecycle. Agile
    processes harness change for the customer's competitive advantage. (Does not change)
  25. 25Which are the Third principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Deliver working solutions(software) frequently, from a couple of weeks to a couple of
    months, with a preference to the shorter time scale.
  26. 26Which are the Fouth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Stakeholders(Customers) and developers must work together daily throughout the project. (not only business stakeholders)
  27. 27Which are the Fifth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Build projects around motivated individuals. Give them the environment and
    support they need, and trust them to get the job done.(Remains the same)
  28. 28Which are the sixth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)The most efficient and effective method of conveying information to and within a
    delivery team is face-to-face conversation.(Remains the same)
  29. 29Which are the seventh principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Consumable solutions(Working software) are the primary measure of progress.
  30. 30Which are the eighth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Agile processes promote sustainable delivery. The sponsors, developers, and users
    should be able to maintain a constant pace indefinitely. (Remains the same)
  31. 31Which are the nineth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Continuous attention to technical excellence and good design enhances agility.(Remains the same)
  32. 32Which are the tenth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)Simplicity – the art of maximizing the amount of work not done – is essential.(Remains the same)
  33. 33Which are the eleventh principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)The best architectures, requirements, and designs emerge from self-organizing
    teams.(Remains the same)
  34. 34Which are the twelveth principal of disciplined agile ?(DAD Principles – Extending the Twelve Principles of Agile Software)At regular intervals, the team reflects on how to become more effective, then
    tunes and adjusts its behavior accordingly.(Remains the same)
  35. 35how many changes do DAD to the principles in the original manifesto(DAD Principles – Extending the Twelve Principles of Agile Software)Change 4 original principles(1,3,4 y 7) and add three more to complete 15 principles.
  36. 36Which principles were added to the diciplined agile (DAD Principles – Extending the Twelve Principles of Agile Software)13. Leverage and evolve the assets within your enterprise, collaborating with the
    people responsible for those assets to do so.
    14. Visualize work to produce a smooth delivery flow and keep work-in-progress (WIP)
    to a minimum.
    15. Evolve the enterprise to support agile, non-agile, and hybrid teams.
  37. 37Which ones are radical agile ideas?• Do the simplest thing possible and no more
    • Changing requirements are a good thing
    • Teams should have all the skills and knowledge required to
    get the job done
    • Less is often more – Keep all artifacts as lightweight as possible
    • Capture detailed requirements and designs as executable
    tests, not written documents or models
    • Collaboration is critical to your success
    • Test often and early, and better yet test first
    • Non-solo work is more effective than people working alone
    • Too much up front modeling and planning increases project
    risk
    • Learn from your experiences, and evolve your strategy as the
    project progresses
    • Stakeholders have greater visibility into an agile project and
    greater opportunities to guide the team
  38. 38which ones are Lean startup practices?- Minimum viable product
    - Persevere or Pivot
    - Split testing
    - Continuous deployment
    - Actionable metrics
    (book recommended The lean startup of Eric ries)
  39. 39What is the dad term of Iteration(XP Term), Sprint(Scrum term) and Iteration(UP term ) ?Iteration
  40. 40What is the dad term of Coach(XP Term), Scrum master(Scrum term) and project mannager(UP term ) ?Team lead, becareful with the roles of scrum master and project manager because they arent the same
  41. 41What is the dad term of Daily meeting(XP Term), daily scrum metting(Scrum term) and meeting(UP term ) ?Coordination Meeting
  42. 42What is the dad term of Retrospective(XP Term), Sprint retrospective(Scrum term) and Retrospective(UP term ) ?Retrospective
  43. 43What is the dad term of Demo(XP Term), Sprint Review(Scrum term) and Demo(UP term ) ?Demo
  44. 44Which are the main characteristic of DAD?– People-first
    – Goal-driven
    – Hybrid agile
    – Learning-oriented
    – Full delivery lifecycle
    – Solution focused
    – Risk-value lifecycle
    – Enterprise aware
  45. 45Which are the Primary Roles on DAD Teams?They are 5 and are:
    Team LeaD
    Product Owner
    Architecture Owner
    Team Member
    Stakeholder
  46. 46Which is the Team Lead rol?Agile process expert, keeps team focused on achievement of goals,
    removes impediments
  47. 47Which is the Product Owner rol?Owns the product vision, scope and priorities of the solution
  48. 48Which is the Architecture Owner rol?Owns the architecture decisions and technical priorities,
    mitigates key technical risks
  49. 49Which is the Team Member rol?Cross-functional team members that deliver the solution
  50. 50Which is the Stakeholder rol?Includes the customer but also other stakeholders such as the
    project sponsor, operations engineers, support staff, architecture,
    database groups, finance, and so on
  51. 51Which are the Secondary Roles on DAD Teams?They are 5 and are:
    -Independent Tester
    -Specialist
    -Domain Expert (Subject Matter Expert)
    -Technical Expert
    -Integrator
  52. 52Which is the Independent Tester rol?A test/quality professional outside of the team who validates their work
  53. 53Which is the Specialist rol?Someone in a specialist role, such as business analyst, program manager, or
    enterprise architect
  54. 54Which is the Domain Expert (Subject Matter Expert) rol?Someone with deep knowledge of the domain, such as a legal expert or
    marketing expert who is brought in as needed to share their expertise
  55. 55Which is the Technical Expert rol?Someone with deep technical knowledge, such as a security engineer or user
    experience (UX) professional, whose help is needed for a short period
  56. 56Which is the Integrator rol?Someone responsible for the operation of the overall team build
  57. 57Which are Google’s Five Keys to Successful Teams-Psychological Safety
    -Dependability
    -Structure & clarity
    -Meaning of Work
    -Impact of work
  58. 58Ask this question in order to know if can reach psycological safety?Can we take risks on this team without feeling insecure or embarrassed?
  59. 59Ask this question in order to know if can reach Dependability?Can we count on each other to do high quality work on time?
  60. 60Ask this question in order to know if can reach Structure & clarity?Are goals, roles, and execution plans on our team clear?
  61. 61Which is a Lean Framework?Kanban
  62. 62Ask this question in order to know if can reach Meaning of Work?Are we working on something that is personally important for each of us?
  63. 63Ask this question in order to know if can reach Impact of work?Do we fundamentally believe that the work we’re doing matters?
  64. 64What producess DAD Teams?Consumable solutions
  65. 65how many people are in Small Teams DAD and what roles?(2 to 15 People)
    1 - Small Dad team(Team leader/Architecture orwner , Team Members, Producto owner)
    2 - Small Dad team(Team leader/Architecture orner , Team Members, Producto owner), supporting cast( TEcnical Experts , Domain experts independint testers.)
  66. 66how many people are in Medium-Sized Teams DAD and what roles?(10 to 30 people)
    1 - Dad team(Team leader ,Architecture orwner , Team Members, Producto owner, Specialist) supporting cast( TEcnical Experts , Domain experts independint testers.)
    2- Dad sub teams(Team leader ,Architecture orwner , Team Members, Producto owner, Specialist) supporting cast( TEcnical Experts , Domain experts independint testers.)
  67. 67What producess DAD sub-Teams on Medium-sized teams and Large Teams?Features/components . all sub teams produces consumable solution
  68. 68how many people are in Large Teams DAD and what roles?(30 people or more)
    1 -leadership team(product delivery, program manager/coordinator, product ownersship, architecture ownership), Dad sub team(Team leader ,Architecture orwner , Team Members, Producto owner, Specialist) supporting cast( Tecnical Experts , Domain experts ,independint testers, integrators)
  69. 69Which are organizational options to Large teams?• Feature teams: A subteam works on a
    feature from end to end.
    • Component teams: A subteam does all
    the work for a specific component.
    • Internal open source: A component is
    developed via open source techniques.
  70. 70What are the four Geographically Distributed/Dispersed Teams options?- Co-located
    -Fully Dispersed
    -Distributed subteams
    -Partially dispersed
  71. 71Why DAD is a DAD is a Hybrid Framework?DAD leverages proven strategies from several sources,
    providing a decision framework to guide your adoption and
    tailoring of them in a context-driven manner. Safe,DevOps, XP,UP,AM,Scrum,kanban,lean,AD, Tradicional,Outside in dev and more
  72. 72In the High-Level Delivery Lifecycle whats the target of inception ?Envision and plan
  73. 73In the High-Level Delivery Lifecycle whats the target of Construction ?Incrementally build a consumable solution
  74. 74In the High-Level Delivery Lifecycle whats the target of Transition ?Release Solution
  75. 75Which are the steps on High-Level Delivery Lifecycle ?- Inception
    - Construction
    - transaction
    Next release (back from transition to Inception)
  76. 76What practices are taking from Scrum?Product Backlog (work item list)
    • Value-driven lifecycle
    • Daily Scrum meeting (coordination meeting)
    • Release Planning
    • Sprint planning (iteration planning)
    • Sprint review and demonstration
    • Sprint retrospective
    • User story driven development
  77. 77Inception Phase can be one o more iterations?Si pero no olvidar que extenderse en esta fase se pueder volver a water -scrum fase documentanto mucho al inicio. lo mas recomendable es algo corto por ejemplo 1 semana
  78. 78Que tiene que estar terminado o entendido para comenzar la fase de contrsticon?Stakeholder Vision
  79. 79Que es lo primero que se tiene que probar en la fase construcion ?La arquitectura
  80. 80Que se tiene que tener para pasar a la fase de transition?Suficiente funcionalidad
  81. 81What phases are in a full lifecicle?- Concect(Envision)
    - inception
    - Construcion
    - Transition -( release solution or next release)
    - Producion (Operate and suport may produce change requets and go to inception phase again)
  82. 82how many cicles has DAD4
    -Agile Lifecycle
    -Lean Lifecycle
    -Agile Continuous Delivery
    Lifecycle
    - Lean Continuous Delivery
    Lifecycle
  83. 83how is called the exploratory cicle on DAD“Lean Startup” Lifecycle
  84. 84What activities has to be continuosly on DAD-Continuous Analysis
    -Continuous Architecture
    -Continuous Design
    -Continuous Development
    -Continuous Governance
    -Continuous User Experience (UX)
    - Continuous Testing
    - Continuous Management
    -Continuous Technical Writing
  85. 85What activities on Inception has to be done in Continuous Analysis?- Initial Requirements
    Envisioning
    - Stakeholder
    Vision
    - Look-ahead
    modeling
  86. 86What activities on Construction has to be done in Continuous Analysis?-Active stakeholder
    participation
    -Look-ahead
    modeling
    -Explore requirements during
    iteration planning
    -Behaviour Driven
    Development (BDD)
    -Identify new needs
    during demos
    -Analysis of incoming
    requests from production
  87. 87What activities on Transition has to be done in Continuous Analysis?Nothing
  88. 88What activities on Inception has to be done in Continuous Architecture?-Initial Architecture
    Envisioning
    -Spikes
    -Stakeholder
    Vision
  89. 89What activities on Construction has to be done in Continuous Analysis?-Prove architecture early
    with working code
    -Spikes
    -Architecture Owner
    facilitates architecture
    sessions
    -Look-ahead
    modeling
    -Architecture
    Handbook
    -Analysis of incoming
    requests from production
  90. 90What activities on Transsition has to be done in Continuous Analysis?Nothing
  91. 91What activities on Inception has to be done in Continuous Design?-Look-ahead
    modeling
    -Spikes
    -Stakeholder
    Vision
  92. 92What activities on Costruction has to be done in Continuous Design?- Explore design during
    iteration planning
    -Look-ahead
    modeling
    -Spikes
    -Test-Driven
    Development (TDD)
    -Mob
    programming
    -Consider design issues for incoming
    requests from production
  93. 93What activities on Transsicion has to be done in Continuous Design?Nothing
  94. 94What activities on Inception has to be done in Continuous Development?-Spikes
  95. 95What activities on Construction has to be done in Continuous Development?-Pair programming
    -Spikes
    -Behavior Driven
    Development (BDD)
    -Test-Driven
    Development (TDD)
    -Mob
    programming
    -Continuous
    Deployment (CD)
    -Continuous
    Integration (CI)
  96. 96What activities on Transsition has to be done in Continuous Development?- Continuous
    Deployment (CD)
  97. 97What activities on Inception has to be done in Continuous Governance?- Stakeholder Vision
    milestone
  98. 98What activities on Construction has to be done in Continuous Governance?-Automated
    team dashboard
    -Proven Architecture
    milestone
    -Demos
    -Go-forward
    decision
    -Project Viability
    milestone
    -Sufficient Functionality
    milestone
    -Active stakeholder
    participation
  99. 99What activities on Transition has to be done in Continuous Governance?-Production Ready
    milestone
    -Delighted Stakeholders
    milestone
  100. 100What activities on Inception has to be done in Continuous User Experience (UX)?- Initial UX
    design
  101. 101What activities on Construction has to be done in Continuous User Experience (UX)?- Iteration modeling
    -Active stakeholder
    participation
    -Look-ahead
    modeling
    -Usability testing
    - Demos
  102. 102What activities on Transsition has to be done in Continuous User Experience (UX)?Nothing
  103. 103What activities on Inception has to be done in Continuous Testing?- Initial test
    -Setup test
    environment(s)
  104. 104What activities on Construction has to be done in Continuous Testing? ?-Whole team testing
    -Test automation
    -Behavior Driven
    Development (BDD)
    -Test-Driven
    Development (TDD)
    -Demos
    -Parallel independent
    testing
  105. 105What activities on Transition has to be done in Continuous Testing?- End-of-lifecycle
    testing
  106. 106What activities on Inception has to be done in Continuous Management?- Initial release
    planning
  107. 107What activities on Construction has to be done in Continuous Management?- Iteration planning
    -Look-ahead
    planning
    -Taskboards
    -Iteration wrap-up
    -Self organization
    -Coordination
    meetings
  108. 108What activities on transition has to be done in Continuous Management?nothing
  109. 109What activities on Inception has to be done in CContinuous Technical Writing?-Determine
    documentation needs
    -Adopt common
    templates
  110. 110What activities on Construction has to be done in Continuous Technical Writing?- Continuous
    documentation
    -Document late
  111. 111What activities on Transition has to be done in Continuous Technical Writing?Nothing
  112. 112What activities has Devops during Develoment on Inception ?- Initial requirements
    envisioning
    -Initial architecture
    envisioning
    -Initial release
    planning
  113. 113What activities has Devops during Develoment on Constrution ?- Active stakeholder
    participation
    -Continuous
    Integration (CI)-
    -Continuous
    Deployment (CD)
    -Deployment
    planning
  114. 114What activities has Devops during Develoment on Transition ?- Production Ready
    milestone
    -Delighted Stakeholders
    milestone
    -Continuous
    Deployment (CD)
  115. 115Which are goals in inception? (how do we start))- Form Initial Team
    -Develop Common Vision
    -Align with Enterprise Direction
    -Explore Initial Scope
    -Identify Initial Technical Strategy
    -Develop Initial Release Plan
    -Secure Funding
    -Form Work Environment
    -Identify Risks
    -Develop Initial Test Strategy
  116. 116Which are goals in Construction? (how do we produce a solution)-Produce a Potentially Consumable Solution
    -Address Changing Stakeholder Needs
    -Move Closer to a Deployable Release
    -Improve Quality
    -Prove Architecture Early
  117. 117Which are goals of Transition?-Ensure the solution is production ready
    -Deploy the solution into production
    -Ensure stakeholders are prepared to receive the solution.
  118. 118Which are goals in ongoing?(what do we do throughout)-Fulfill the project mission,
    -Grow Team Members
    -Govern Delivery Team
    -Leverage and Enhance Existing
    Infrastructure
    -Address Risk
    -Improve Team Process and Environment
    -Coordinate Activities
  119. 119Que indica la flecha hacia arriba en el mapa de metas(goals)Indicates a preference for
    the options towards the top
  120. 120(inception)Which are the points of decicion of Goal: Form Initial Team- Source(Where will team members come from?)
    -team evolution strategy(How do we intend to evolve the team over time?)
    -Size(How large should the team be?)
    -Structure(How will sub-teams be organized (if we need them)?)
    -Members skills(What type of team members do we need?)
    -Longetivity(How long will the team exist?)
    -geographyf dictibution(Where will team members be located?)
    -Support the team(How will we support the team?)
    -Availability(How available will team members be?)
    -Completeness ????
  121. 121(inception)Which are the points of decicion of Goal: Explore Initial Scope- Choose le level of detail(What level of detail do we need to capture?)
    -Explore usage(How will we explore the ways that people will potentially use the solution?)
    -Explore the domain(How will we explore domain concepts, the business process(es) to be supported by the solution, UI requirements, and general requirements?)
    How will we capture non-functional requirements?
    - Aply modeling strategies(How will we approach modeling activities?)
    How will changing requirements be managed throughout Construction?
    -Explore the process
    -Explore User interface needs
    -Explore general requeriments
    -Explore Non-Funtionals
    -Choose a work item management strategy
  122. 122(Construction )Goals: Address Changing Stakeholder Needs-manage work items(How are we going to manage work items?)
    -priorize work (How are we going to prioritize changes?)
    -Accept changes(When are we going to accept any changes?)
    -Stakeholders interacting with team(How will we work with stakeholders?)
    -Elicit requeriments(How will our team elicit feedback from stakeholders)
  123. 123(Ongoing)Goal: Coordinate Activities-Share information( How will we share information within the team?)
    -Artefac ownership/Who is allowed to update the artifacts created by the team?)
    - Coordinate within team(How will we coordinate within the team?)
    - coordinate within rograma(If we’re part of a larger team, how will we coordinate within it?)
    -oordinate across IT(How will we work with enterprise/IT teams such as enterprise architects and data managers?)
    -coordiante release Schedule( How will we coordinate our release/deployment with the rest of the organization?)
    - Coordinate between locations)If we have geographically distributed team members, how will we collaborate with them?)
  124. 124What are the options y default option of Form Initial Team >Source- (default) Existing product team
    - Existing team from another product
    -New
  125. 125What are the options y default option of Form Initial Team >Team Evolution Strategy- (default) Team accepts new members
    -Team lead accepts new membees
    -Management assigns new members
  126. 126What are the options y default option of Form Initial Team >Size- (Default) small
    -medium
    -large
  127. 127What are the options y default option of Form Initial Team >Structure-(default) simple team
    - component teams
    -feature teams
    -internal open source
  128. 128What are the options y default option of Form Initial Team >members skills-(default) Generalizing specialist
    -specialist
    -Generalist
  129. 129What are the options y default option of Form Initial Team >Completeness- (default) Whole Team
    -Specialized team
    -Ad-hoc
  130. 130What are the options y default option of Form Initial Team >Longevity-(default) Stable(product) team
    - project team
    -Ad-hoc
  131. 131What are the options y default option of Form Initial Team >Geographic distribution-(default) co-located
    -partially dispersed members
    -Fully dispersed members
    -Distributed subteams
  132. 132What are the options y default option of Form Initial Team >Support the team-(default) Coaching
    -(default) mentoring
    -(default) Training
    -(default) Stakeholders Access
  133. 133What are the options y default option of Form Initial Team >Availability-(default) dedicated
    -ongoing part time
    -as needed /available
  134. 134What Does it Mean to Be Disciplined?• It requires discipline to follow many
    agile practices and philosophies
    • But, it also requires discipline to: – Reduce the feedback cycle – Learn continuously – Deliver solutions incrementally – Be goal driven – Enterprise aware – Streamline Inception and
    Transition efforts – Adopt agile governance strategies
  135. 135What is the Disciplined Agile (DA) Framework?Disciplined Agile (DA)
    is a process decision framework
    providing light-weight guidance
    enabling organizations to streamline their processes in a context-
    sensitive manner
    while providing a solid foundation for business agility
  136. 136Teams that are “enterprise aware” will:-Support open and honest monitoring
    -Leverage enterprise assets
    - Ensure your organization ecosystem
    -Share team learning
    Enterprise awareness is an important aspect of self-discipline because as a professional you should strive to do what’s right for your organization and not just what’s interesting for you.
    We can and should do better by doing the following: Leveraging enterprise assets, Enhancing your organizational ecosystem, Sharing learnings, Open and honest monitoring
  137. 137Requirements can be written as executable tests?True :an alternative to writing requirements specifications is to write your requirements as executable tests.
  138. 138The team lead role is similar to the Scrum Master role?yes, the team lead role is similar to the Scrum master role who is involved in coaching the team to achieve desired goals.
  139. 139The suggested approaches to select a Work Item are:Following are the suggested approaches to select a work item:
    - Business value
    - Risk
    -Due date
    -Operational emergency
    -Dependencies.
  140. 140Non-solo development is an extension of XP’s pair programming practice.Non-solo development is an extension of XP’s pair programming practice. DAD extends the idea to include all team members, suggesting that working in pairs, regardless of specialty, often makes sense, increasing both productivity and quality
  141. 141Identifying a project vision includes:Brining stakeholders to agreement
    Capturing project vision
    Strategy will evolve throughout your project
    (Big up-front documentation exercise is not recommended )
  142. 142The activities in your Transition phase are unique to the type of solution:The activities in Transition phase are unique to the type of solution that you are deploying and the degree of governance for managing deployments in organization.
    You should take some time at the beginning of the phase to do an iteration planning workshop to plan your work for the phase.
  143. 143Implementing “agile governance” results in agile teams being easier to govern than traditional teams?Appropriate governance strategies should enhance the ability of DAD teams to deliver business value to their stakeholders in a cost effective and timely manner.
  144. 144Disciplined Agile Delivery (DAD) framework:DAD is a three-phase lifecycle where you incrementally build a consumable solution over time. DAD is a Hybrid Framework, DAD leverages proven strategies from several sources, providing a decision framework to guide your adoption and tailoring of them in a context-driven manner. the team members gain beyond their primary discipline results in more effective use of resources and reduced reliance on formal documentation and handoffs.
    There should be no hierarchy within the team, and team members are encouraged to be cross-functional in their skillset and indeed perform work related to disciplines other than their specialty.
  145. 145Which of the following are typical on-going activities through each day of a construction iteration?Following are the are typical on-going activities through each day of a construction iteration:
    -Creating deliverable documentation
    -Non-solo development
    -Collective ownership
    -Configuration management
    -Change management
    -Updating task progress
    -Team leadership
    -Sustainable pace
    -Automated metrics gathering
    -Following organizational standards
  146. 146One of the strategies for capturing the project vision is called “information radiators”The practice of displaying information on all things related to the project is known as visual management, big visible charts, and information radiators (by Alistair Cockburn).
  147. 147Transition activities such as procuring production environments, preparing a support team, and training for the new system and potentially changed business processes need to occur always during transition phase:Some work related transition activities such as procuring production environments, preparing a support team, and training for the new system and potentially changed business processes need to occur during your last Construction iterations prior to the Transition phase actually starting.
  148. 148Which of the following are recommended DAD terms?Product Owner, Architecture Owner, Team lead, Team Member are included in the DAD primary roles.
    Coordination meeting: Throughout the iteration the team organizes their activities on a regular basis, typically at least once a day, via short coordination meetings.
  149. 149According to Scott Ambler’s 2010 Agile State of Art survey, the average experienced team uses an average iteration length of:51% of teams uses 2 weeks of iteration length
  150. 150The approaches that you can take in writing code worth considering:The approaches in writing code worth considering are:
    -Test-driven development (TDD).
    -Test after development
    -Code now, fix later.
  151. 151Key components of communication and training that you should consider to prepare your stakeholders for the solution:Following are the key components of communication and training that you should consider to prepare your stakeholders for the solution:
    -Communicate deployment to stakeholders.
    -Train/educate stakeholders.
    -Prepare support environment stakeholders.
  152. 152Ensuring Your Production Readiness includes:Following are the Production readiness factors:
    -Transition planning.
    -End of lifecycle testing and fixing.
    -Deployment testing.
    -Data migration preparation.
    -Pilot/beta of the solution.
    -Finalize documentation
  153. 153One of the DAD strategies for motivating your team when problem occur is for the Team Lead to use “command and control” techniquesEffective governance in knowledge-based endeavors is based on motivation and enablement, not command and control.
  154. 154The approaches to plan and report the status of your iteration’s work are:The approaches to plan and report the status of your iteration’s work are:
    -Daily coordination meeting
    -Coordination meeting
    -Weekly status
    -No scheduled meeting
  155. 155Coordination Meeting is similar to Daily Scrum meeting?True:A typical day begins with a short coordination meeting, is followed by the team collaborating to do their work, and concludes with a working build (hopefully) at the end of the day. It is similar to Daily Scrum meeting of Scrum framework.
  156. 156The suggested (default) approach to capturing initial requirements is:Goal driven approach Provides the team with significant flexibility as to how they approach providing a solution. Can and should be used with the more detailed approaches.
  157. 157Which one of the following are typical strategies for effective teams?Following are the strategies for effective teams:
    -Are focused.
    -Are tailored to the environment.
    -Are based on trust and respect.
    -Are safe.
    -Provide learning opportunities
    -Are as small as possible.
    -Have shared workspaces.
    -Are “whole.”
    -Are self-organizing within the constraints of appropriate governance.
    -Have adequate resources to fulfill their remit.
    -Are accountable.
    -Are self-aware.
    -Are enterprise aware
    -Include dedicated people.
    -Are geographically close.
    -Follow a common strategy.
    -Stay together.
  158. 158Which one of the following are the techniques for validating the solution?There are many agile testing approaches that you can take to integrate each developer’s work and validate that it works as an integrated solution. These approaches include
    -Acceptance test-driven development (ATDD).
    -Continuous integration.
    -User interface (UI) testing.
    -Parallel independent testing.
    -End-of-lifecycle testing.
    -Code/schema analysis.
    -Reviews/inspections.
    -Nonfunctional testing.
    -Manual testing from detailed test case specifications.
    -None: An appropriate strategy for those who feel that success is optional.
  159. 159There is a need to collaborate continuously with stakeholder’s external to the team to prepare and minimize the deployment risks.DAD takes a disciplined approach to managing your solution’s deployments and recognize the need to collaborate continuously with stakeholder’s external to the team to prepare and minimize the deployment risks. Adequate attention to testing your deployments before the Transition phase starts helps to ensure that your deployment goes smoothly.
  160. 160Which of the following are DAD secondary role?There are five secondary roles on DAD project teams (Specialist, Domain Expert, Technical Expert, Independent Tester, Integrator). The secondary” DAD roles typically occur at scale.
  161. 161approaches that you can take to plan and report the status of your iteration’s work.- Daily coordination meeting
    - Weekly status meeting
  162. 162approches you can take to integrate each developer’s work and validate that it works as an integrated solution.- Continuous integration.
    - Parallel independent testing.
  163. 163Which are high level activities for deploying the solution.-Running of any batch jobs against the existing system.
    - Enable your support system
  164. 164which is important for having stakeholders delighted.Business stakeholder acceptance
  165. 165Which are approaches that you can take to elaborating your requirements during construction-Create acceptance tests.
    - Look-ahead modeling of requirements
  166. 166The key characteristics of DAD:People-first
    Goal-driven
    Hybrid agile
    Learning-oriented
    Full delivery lifecycle
    Solution focused
    Risk-value lifecycle
    Enterprise aware
  167. 167Which of the following are the responsibilities of the Product Owner?The product owner is the one individual on the team who speaks as the “one voice of the customer.”
    He is typically gateway to funding, “go to” person for domain information, involved in continually reprioritizes and adjusts scope. He is typically collocated with the project team and also an active participant in modelling and acceptance testing.
  168. 168Which of the following are the benefits of doing some initial architectural modelling at the beginning of an agile project?-Improved productivity.
    -Reduced technical risk.
    -Technical debt avoidance.
    -Improved enterprise awareness.
    -Improved development/operations (DevOps) integration.
    -Reduced development time.
    -Address the nonfunctional “ilities” early.
    -Improved communication.
    -Scaling agile software development.
  169. 169Architecture and testing, occur iteratively and incrementally throughout the Construction phase.true:A critical point to understand is that the activities of traditional development disciplines, such as architecture and testing, occur iteratively and incrementally throughout the Construction phase.
  170. 170Considerations of choosing iteration length includes:51% of teams uses 2 weeks of iteration length. All other options are important to consider while choosing iteration length.
  171. 171Which of the following are considered potential issues when scaling DAD?-Geographical distribution
    -Team size.
    -Regulatory compliance
    -Domain complexity
    -Technical complexity.
    -Organizational distribution
    -Organizational complexity.
    -Enterprise discipline.
  172. 172Which you should achieve at Stakeholder Delight milestone?At Stakeholder Delight milestone, you should achieve the following:
    -Business stakeholder acceptance.
    -Operations acceptance.
    -Support acceptance.
    -Cost and estimate acceptance.
  173. 173Goals for the inception phase are:Inception phase goals are form initial team, develop common vision, align with enterprise direction, explore initial scope, identify initial technical strategy, develop initial release plan, secure funding, form work environment, and identify risks.
  174. 174Which of the following are goals of construction?Produce a potentially consumable solution, Address changing stakeholder needs, move closer to a deployable release, Maintain or improve upon existing levels of quality, Prove architecture early.
  175. 175Construction pattern for success includes:The construction phase patterns include:
    -The team can be reliably depended on to demonstrate increments of software at the end of each iteration.
    -Team members finish their tasks ahead of schedule and ask to help others with their tasks
    -Iteration dates never move
    -Any stakeholder can walk into the common work area and request to see a demonstration of the working software as it currently sits, at any time
  176. 176Transition Phase Patterns includes:Following are the Transition patterns:
    -Short and sufficient.
    -Multiple iterations.
    -Proven deployment/installation.
    -Choose your release patterns
  177. 177Anti-patterns for construction includes:-A work item list that is too big to easily manage and comprehend.
    -Inattention to risk mitigation.
    -Assuming that the architecture will work without proving it with code.
    -Assuming that an iterative approach alone ensures that you will build the right solution in an effective manner.
    -One or more of your team members are working on other projects in addition to yours.
    -A work item isn’t done.
    -Defect counts are increasing in each iteration.
  178. 178Transition Phase Anti-Patterns includes:-Not having a production like environment for integration, acceptance, and deployment testing.
    -Not having an agreed upon set of entry criteria for going “live.”
    -Requests for new functionality.
    -Releasing the system to unprepared users.
    -Lengthy integration and user acceptance testing (UAT) cycle in Transition.
    -Transferring responsibility for maintaining the system to a maintenance group.
    -Moving all of your developers to another project at the end of Construction.
    -Not investing in stakeholder training.
    -Believing that installation is going to be easy.
  179. 179Inception Phase Patterns includes:Short and sufficient, ranged estimates and Minimal but sufficient documentation are patterns for success.
  180. 180Inception Phase anti-Patterns includes:Inception phase anti patterns includes: No support for skills development, no support for dedicated facilities, Autocratic project management practices, Jumping into Construction, Overly detailed work products, Analysis paralysis.
  181. 181Which one of the following is the characteristics of Good Teams when DAD teams commit only to the work which they can accomplish and then perform that work as effectively as possibleSelf-disciplined, in that they commit only to the work which they can accomplish and then perform that work as effectively as possible.
  182. 182DAD teams and team members should be:-Self-disciplined, in that they commit only to the work which they can accomplish and then perform that work as effectively as possible.
    -Self-organizing, in that they will estimate and plan their own work and then proceed to collaborate iteratively to do so.
    -Self-aware, in that they strive to identify what works well for them, what doesn’t, and then learn and adjust accordingly.
  183. 183Architecture can support only non-functional requirements?false:In Construction we need to prove that the architecture can indeed support both the functional and non-functional requirements by implementing stories that have good architectural coverage.
  184. 184You may schedule multiple deployments in Transition”true:At some point during your Transition phase you will choose to deploy your solution to your stakeholders. In fact, you may schedule multiple deployments in Transition if a phased deployment makes sense, such as in the case of delivery across geographies.
  185. 185Teams is not necessarily requiring to have all the skills and knowledge required to get the job done?true:Teams should have all the skills and knowledge required to get the job done.
  186. 186What is a Diciplined agile delivered?It is a process decision framework
  187. 187Where the secondary roles are having into account?tipically occur at scale
  188. 188which ones are advances practices commonly applied but for some reason nor commonly discussed by agile communite?- Initial requirements envision
    - initial architecture envisioning
    - end-of-lifecycle testing
    and more
  189. 189which are three charateristic of DAD Teams?- Self-diciplined
    - Self-organizing
    - Self-aware
  190. 190Which words are not like Agilist?Governance
    Documentation
    phases
    and more
  191. 191Is it DAD oriented to product development?The focus of DAD is not product development, even though a tailored form of DAD is being applied for that within IBM, nor is it on system enginering.
  192. 192Whats the focus of the book?on IT application development
  193. 193Which are the critical charateristic of the diciplinary agile delivery DAD lifecycle- it is a deliverable cycle(into production or marketplace)
    - there are explicit phases(refleting the agile coordinated-collaborate-conclude 3c rhythm)
    - the delivery lifecycle is shown in context
    -there are explicitit milestones
  194. 194Cual ciclo es el mejor para empezar en equipos que son nuevos en dad o aun nuevos en agile?the diciplinary agile delivery DAD lifecycle also knonw as basic agile version
  195. 195Which strategy works well to highly diciplined teams?Lean version of the DAD lifecycle
  196. 196Whats the primary diferrence of agile version(the diciplinary agile delivery DAD lifecycl) and lean version?that phase and iteration cadence disappears in favor of a " do it when you need to do it" approach.
  197. 197Which is a similar concept to Demings plan,do,check,act?the agiel 3c rhytthm for coordinate , collaborate and conclude
  198. 198What is the diferrence view between a agile point and lean point repect to transcition?for agile transsiciont point ends when the satakeholders are ready and the system is fully deploy. from a lean point of view, the phase ends when stakeholders hae worked with the solution in production and are delighted by it.
  199. 199Why dad is risk and value drive?value driven because reduces de delivery risk producing potencially consumable solutions on a regular basis. and risk driven address some common risk as stakeholder consensus around the vision and proving thr architecture early in a lifecycle
  200. 200Why others features are said that dad is value drive?because it address three important risk
    - the risk of not delivering at all
    - the risk of delivering the wrong funcionality
    -political risk resulting from lack of visibility into what the team is producing

Information

Description
Certificado PMP (Dirección de Proyectos) Dirección de Proyectos Flashcards on Dad Certification(Part 1), created by Carlos Andres Garcia on 22/03/2018.
Views
19
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?