This blog contains details about various aspects of PMI's Disciplined Agile (DA) tool kit, including new and upcoming topics.
View Posts By:
Tatsiana Balshakova Mark Lines Mike Griffiths Scott Ambler Bjorn Gustafsson Curtis Hibbs James Trott
Past Contributors:
Joshua Barnes Michael Richardson Daniel Gagnon Valentin Tudor Mocanu Kashmir Birk Glen Little Klaus Boedker
Recent Posts
DA 5.6 is released
Disciplined Agile 5.5 Released
Choose Your WoW! Second Edition Is Now Available
Requisite Agility applied in Project Management
Disciplined Agile and PMBoK Guide 7th Edition
Categories
#ChoiceIsGood #ChooseYourWoW #ConsumableSolution #ContinuousImprovement #CoreAgilePractices #experiment #Experimentation #GuidedContinuousImprovement #Kaizen #LifeCycles #ProcessImprovement #TealOrganizations Adoption agile agile adoption Agile Alliance Agile Business Analyst Agile certification agile data agile governance agile lifecycle agile metrics agile principles agile transformation Agile2018 Agile2019 Agile20Reflect AgileData Analogy announcement Architecture architecture architecture owner Articles and publications Asset Management Atari Backlog Barclays being agile benefits bi blades book Branching strategies Browser Business Agility business intelligence business operations capex Case Study Certification certification charity Choose your WoW CMMI cmmi Coaching Collaboration Communications Management Compliance Compliancy Conference Construction Construction phase Context Continuous Improvement coordination COVID-19 Culture culture Cutter DA DAD DAD Book DAD discussions DAD press DAD roles DAD supporters DAD webcast DADay2019 Data Management database dependencies Deployment Development Strategies DevOps disaster Discipline discipline Disciplined Agile disciplined agile delivery disciplined agile delivery blog Disciplined Agile Enterprise disciplined devops Documentation Domain complexity dw DW/BI Energy Healing Enterprise Agile Enterprise Architecture Enterprise Awareness enterprise awareness Essence estimation Evolving DA Executive Experiment facilitation FailureBow feedback-cycle finance Financial FLEX Flow foundation layer Funding GCI GDD Geographic Distribution gladwell global development Goal-Driven goal-driven goals Governance GQM Guideline Hybrid Improvement inception Inception phase India information technology infosec Introduction iterations Kanban large teams layer lean Lean Startup learning Legal Project Management LeSS Lifecycle lifecycle Manifesto mark lines marketing MBI Metaphor Metrics metrics mindset Miscellaneous MVP News News and events Non-Functional Requirements non-functional requirements Non-solo development offshoring Operations opex Organization Outsourcing outsourcing paired programming pairing paper People People Management phases Philosophies Planning PMBoK PMI PMI and DA PMI Chapter Portfolio Management post-format-quote Practices practices Principle Process process improvement process tailoring Product Management product owner Product Owners productivity Program Management Project Management project-initiation Promise Quality quality rational unified process Refactoring Reiki Release Management release management Remote Training Remote Work repeatability requirements Requirements Management research&development responsibilities retrospectives Reuse Reuse Engineering ride for heart rights Risk Management Risk Management Risk management Roles RUP SAFe sales Scaling scaling scaling agile Scheduled Workshops SCM scorecard Scrum ScrumMaster SDLC Security security self-organization SEMAT serial skill solutions software consumable shippable Stakeholder Management strategy Support Surveys Teal organizations team development Team Lead team lead Teams Technical Debt Teleconferencing Terminology terraforming test strategy testing time tracking Tool kit Toolkit tools traditional Transformation Transition iteration transition phase Uncategorized Upmentors Using PMI Standards value stream velocity vendor management Virtual Training Workflow workflow workspaces
Date
Some would argue that effective agile teams have all the skills internally to deliver the solution. Is it practical to expect the project team to have control over all aspects of the project such as architecture, database designs and so forth? Or should agile teams take some time to consult with authorities such as PMOs (to understand required governance), DBAs (to evolve a common database, or find existing data sources), and Enterprise Architecture groups (to discover existing assets for reuse, or contribute new ones)?
Take Our Poll
Posted
by
Mark Lines
on: September 02, 2011 03:39 PM |
Permalink
